Use-after-free vulnerability in atm: nicstar

Kernel Updated 02 Oct 2025

Summary

03/08/2021
N/A
No i
Unrated
Not published

GSD-2021-1001357: atm: nicstar: Fix possible use-after-free in nicstar_cleanup(). Affects Kernel versions < bdf5334250c69fabf555b7322c75249ea7d5f148. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The atm: nicstar package is a component of the Linux Kernel, which is responsible for handling Asynchronous Transfer Mode (ATM) network interfaces. It provides the necessary drivers and functionality for ATM network cards. The nicstar_cleanup() function within the package is susceptible to a use-after-free vulnerability.

Vulnerability Detail

The use-after-free vulnerability in atm: nicstar arises from improper memory management in the nicstar_cleanup() function. This vulnerability could be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. The vulnerability has been fixed in Linux Kernel version v5.4.133 by commit bdf5334250c69fabf555b7322c75249ea7d5f148.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.133 or later. This can be done by pulling the latest updates from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their Linux distribution to provide an updated package that includes the fix.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the fix by updating the Linux Kernel.

Conclusion

The use-after-free vulnerability in atm: nicstar has been identified and fixed in Linux Kernel version v5.4.133. It is crucial to update the Linux Kernel to protect systems from potential exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

atm: nicstar is a component of the Linux Kernel that handles ATM network interfaces.

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed, leading to potential security issues.

This vulnerability could allow an attacker to execute arbitrary code or cause a denial-of-service condition on a system running the vulnerable version of atm: nicstar.

Yes, the vulnerability has been fixed in Linux Kernel version v5.4.133 by commit bdf5334250c69fabf555b7322c75249ea7d5f148.

To update the Linux Kernel, you can pull the latest updates from the official Linux Kernel repository and rebuild the kernel. Alternatively, you can wait for your Linux distribution to provide an updated package that includes the fix.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.133 or later. This can be done by pulling the latest updates from the official Linux Kernel repository and rebuilding the kernel. Alternatively, users can wait for their Linux distribution to provide an updated package that includes the fix.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.