NULL Pointer Dereference in llcp_sock_getname() after Failed Connect in nfc
Summary
UVI-2021-1000815: nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect. Affects Kernel versions >= d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 0c4559736d9a4ec1ca58ba98ca34e7c4da4c422b. 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 fundamental component of the Linux operating system that provides core functionalities and manages system resources. It acts as an interface between the hardware and software layers, enabling communication and coordination between various components. The NFC (Near Field Communication) subsystem in the Kernel allows devices to establish short-range wireless communication. One of the functions in the NFC subsystem is llcp_sock_getname(), which retrieves the name of a socket. However, a vulnerability exists in this function that leads to a NULL pointer dereference after a failed connection attempt.
Vulnerability Detail
The vulnerability arises due to a NULL pointer dereference in llcp_sock_getname() after a failed connect operation. When a connection attempt fails, the function does not properly handle the error condition, resulting in a NULL pointer being dereferenced. An attacker could exploit this vulnerability by sending specially crafted packets to a vulnerable system, causing a NULL pointer dereference and potentially leading to a system crash or other adverse effects. 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 →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, a vulnerability has been identified in the NFC subsystem of the Linux Kernel, specifically in the llcp_sock_getname() function. This vulnerability could potentially lead to a system crash or other adverse effects. It is crucial to update the Kernel to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, it could potentially lead to a system crash or other adverse effects.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
There is no known exploit for this vulnerability at the moment. However, it is always recommended to apply security patches and updates to mitigate any potential risks.
The vulnerability was introduced in version v3.3 of the Kernel by commit d646960f7986fefb460a2b062d5ccc8ccfeacc3a. It has been fixed in version v5.12.10 by commit 0c4559736d9a4ec1ca58ba98ca34e7c4da4c422b. Therefore, versions between v3.3 and v5.12.10 are likely to be affected.
If your system is affected, it is recommended to update your Kernel to the latest version available. This will ensure that the vulnerability is patched and your system is protected.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
