NFC: digital: fix possible memory leak in digital_tg_listen_mdaa() - Kernel
Summary
UVI-2021-1001933: NFC: digital: fix possible memory leak in digital_tg_listen_mdaa(). Affects Kernel versions >= 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8, < a67d47e32c91e2b10402cb8c081774cbf08edb2e. 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 Kernel is a crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential functionalities and services to enable the proper functioning of the system. One of its features is the Near Field Communication (NFC) subsystem, which allows devices to communicate wirelessly over short distances. The digital_tg_listen_mdaa() function within the NFC digital driver is responsible for handling the listening mode for NFC target devices. However, a potential memory leak has been identified in this function, which could lead to resource exhaustion and system instability.
Vulnerability Detail
The vulnerability in digital_tg_listen_mdaa() arises from a possible memory leak. When this function is called, it may allocate memory for certain operations but fail to deallocate it properly under certain conditions. This can result in a gradual accumulation of unreleased memory, leading to resource exhaustion and potential system crashes. While the impact and exploitability of this vulnerability have not been proven, it is essential to address it to ensure system stability and prevent potential security risks.
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
In conclusion, the NFC digital driver in the Linux Kernel is susceptible to a potential memory leak in the digital_tg_listen_mdaa() function. This vulnerability can lead to resource exhaustion and system instability. To mitigate this issue, it is crucial to update the Kernel to version v4.9.288 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can potentially lead to resource exhaustion and system instability. However, the actual impact and exploitability have not been proven.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel to the patched version.
The vulnerability was introduced in version v3.13 of the Linux Kernel by commit 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8. It is fixed in version v4.9.288 and later.
You can find more information about this vulnerability in the Open Source Vulnerability database maintained by the Cloud Security Alliance. The vulnerability ID is UVI-2021-1001933.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
