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-1001302: atm: nicstar: Fix possible use-after-free in nicstar_cleanup(). Affects Kernel versions < a7f7c42e31157d1f0871d6a8e1a0b73a6b4ea785. 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 managing ATM (Asynchronous Transfer Mode) network interfaces. The nicstar module provides support for NICStAR-based ATM cards. These cards are used to connect computers to ATM networks, enabling high-speed data transfer. The vulnerability identified in this package is a use-after-free issue, which can lead to potential security risks.

Vulnerability Detail

The use-after-free vulnerability in atm: nicstar is caused by improper memory management. Specifically, the issue arises in the nicstar_cleanup() function, where a reference to freed memory is still being accessed. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet.

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 →

Conclusion

The use-after-free vulnerability in atm: nicstar can pose potential security risks, including arbitrary code execution or denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.10.51 or later to mitigate 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 computer connectivity to ATM networks.

A use-after-free vulnerability occurs when a program continues to reference memory after it has been freed. This can lead to various security risks, including arbitrary code execution or denial-of-service attacks.

The nicstar_cleanup() function is a part of the atm: nicstar package in the Linux Kernel. It is responsible for cleaning up resources and freeing memory used by the NICStAR-based ATM cards.

If exploited, this vulnerability could allow an attacker to execute arbitrary code or cause a denial-of-service condition on a system using atm: nicstar. However, the actual impact and attack plausibility have not been proven yet.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.51 or later, which includes the necessary fix for the use-after-free issue in atm: nicstar.

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