NFC: digital: Fix Possible Memory Leak in digital_tg_listen_mdaa()

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1001828: NFC: digital: fix possible memory leak in digital_tg_listen_mdaa(). Affects Kernel versions >= 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8, < 7ab488d7228a9dceb2456867f1f0919decf6efed. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The NFC (Near Field Communication) subsystem in the Linux Kernel provides support for communication between devices over short distances. The digital_tg_listen_mdaa() function is a part of the digital driver in the NFC subsystem. It is responsible for handling the Target Mode Activation (TMA) requests from an NFC reader. However, a vulnerability has been discovered in this function that could lead to a memory leak.

Vulnerability Detail

The vulnerability in digital_tg_listen_mdaa() can result in a memory leak. When a TMA request is received, the function allocates memory to handle the request. However, if an error occurs during the processing of the request, the allocated memory is not properly freed, leading to a memory leak. This can potentially exhaust system resources and cause instability or denial of service. The vulnerability was introduced in Linux Kernel version v3.13 and has been fixed in version v5.4.155.

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 mentioned for this vulnerability. The recommended approach is to update the Linux Kernel to the fixed version.

Conclusion

The vulnerability in digital_tg_listen_mdaa() of the NFC subsystem in the Linux Kernel can lead to a memory leak, potentially causing system instability or denial of service. It is crucial to update the Linux Kernel to version v5.4.155 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

NFC (Near Field Communication) is a technology that allows devices to communicate with each other over short distances, typically within a few centimeters. It is commonly used for contactless payments, data transfer, and other applications.

digital_tg_listen_mdaa() is a function in the digital driver of the NFC subsystem in the Linux Kernel. It handles Target Mode Activation (TMA) requests from an NFC reader.

A memory leak occurs when a program or system fails to release memory that is no longer needed. This can lead to a gradual loss of available memory, potentially causing performance issues or system instability.

The memory leak vulnerability in digital_tg_listen_mdaa() can result in the exhaustion of system resources, potentially leading to system instability or denial of service. It is important to patch the vulnerability to ensure the system's stability and security.

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, and you can upload your manifest file (e.g., package-lock.json) to check for vulnerabilities without requiring access to the code or installation.

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