NFC: digital: Fix Possible Memory Leak in digital_tg_listen_mdaa()
Summary
UVI-2021-1002155: NFC: digital: fix possible memory leak in digital_tg_listen_mdaa(). Affects Kernel versions >= 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8, < 58e7dcc9ca29c14e44267a4d0ea61e3229124907. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The NFC (Near Field Communication) functionality in the Linux Kernel allows devices to communicate wirelessly over short distances. The digital_tg_listen_mdaa() function is responsible for handling the digital target listen mode activation. However, a vulnerability has been identified in this function that could lead to a memory leak. This vulnerability was introduced in Linux Kernel version v3.13 and is present until version v5.15.
Vulnerability Detail
The vulnerability in digital_tg_listen_mdaa() can result in a memory leak. A memory leak occurs when memory is allocated but not properly deallocated, leading to a gradual reduction in available memory. If this vulnerability is exploited, it could potentially cause memory exhaustion, impacting system performance and stability. The exact attack vectors and impact are yet to be proven.
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 NFC digital_tg_listen_mdaa() function in the Linux Kernel is vulnerable to a memory leak issue. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v5.15 or later. This update will address the memory leak and ensure system stability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially lead to memory exhaustion, affecting system performance and stability.
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 Vulert will analyze it for any open-source vulnerabilities, including this one.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the latest version to fix the issue.
At the time of this report, no known exploits for this vulnerability have been identified.
You can find more information about this vulnerability in the Linux Kernel security advisory or the CVE database by searching for the vulnerability ID UVI-2021-1002155.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
