NFC: digital: fix possible memory leak in digital_tg_listen_mdaa() - Kernel

Kernel Updated 02 Oct 2025

Summary

28/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001784: NFC: digital: fix possible memory leak in digital_tg_listen_mdaa(). Affects Kernel versions >= 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8, < a67d47e32c91e2b10402cb8c081774cbf08edb2e. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and ensures the stability and security of the system. NFC (Near Field Communication) is a technology that enables short-range wireless communication between devices. The digital_tg_listen_mdaa() function in the NFC digital driver is responsible for listening to target devices. However, a possible memory leak has been identified in this function, which could lead to resource exhaustion and potential system instability.

Vulnerability Detail

The vulnerability in digital_tg_listen_mdaa() arises from a potential memory leak. When this function is called, it may allocate memory but fail to release it properly under certain conditions. This can result in a gradual accumulation of unreleased memory, leading to resource exhaustion and potential system crashes or instability. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges.

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

There is no specific workaround provided for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the recommended version.

Conclusion

The vulnerability in digital_tg_listen_mdaa() of the Kernel can lead to memory leaks, resource exhaustion, and potential system instability. It is crucial to update the Linux Kernel to version v4.9.288 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

The vulnerability can lead to resource exhaustion and potential system crashes or instability. It may also allow an attacker to execute arbitrary code with elevated privileges.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the Vulert Playground will analyze it for open-source vulnerabilities, including this one.

No, the vulnerability was introduced in version v3.13 by commit 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8 and fixed in version v4.9.288 by commit a67d47e32c91e2b10402cb8c081774cbf08edb2e. It is recommended to update to the fixed version to mitigate the vulnerability.

There is no known exploit for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to prevent potential exploitation.

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