Use-after-free vulnerability in atm: nicstar

Kernel Updated 02 Oct 2025

Summary

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

UVI-2021-1001490: atm: nicstar: Fix possible use-after-free in nicstar_cleanup(). Affects Kernel versions < 99779c9d9ffc7775da6f7fd8a7c93ac61657bed5. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 support for NICStAR-based ATM cards. These cards are used to connect computers to ATM networks, enabling high-speed data transfer. The nicstar_cleanup() function in 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 can be triggered when the function attempts to free a previously allocated memory block that has already been freed. By manipulating the memory state, an attacker can potentially gain control over the execution flow of the program.

How To Fix

No fixed version is published for this vulnerability.

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

Workaround

As this vulnerability has been fixed in the Linux Kernel, there is no specific workaround available. However, users who are unable to immediately update their kernel can mitigate the risk by implementing other security measures, such as network segmentation, access controls, and intrusion detection systems.

Conclusion

The use-after-free vulnerability in atm: nicstar can be mitigated by updating the Linux Kernel to a version that includes the necessary patch. It is crucial to promptly apply the fix to prevent potential exploitation of this vulnerability. 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 provides support for NICStAR-based ATM cards, enabling high-speed data transfer over ATM networks.

A use-after-free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to unpredictable behavior, including crashes, data corruption, and potential code execution by an attacker.

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.

To fix this vulnerability, update the Linux Kernel to version v4.4.276 or later, which includes the necessary patch to address the use-after-free vulnerability.

While there are no specific workarounds for this vulnerability, implementing additional security measures such as network segmentation, access controls, and intrusion detection systems can help mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

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