Vulnerability in Kernel: nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect
Summary
GSD-2021-1000718: nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect. Affects Kernel versions >= d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < eb6875d48590d8e564092e831ff07fa384d7e477. 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 critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the overall stability and security of the system. The NFC (Near Field Communication) subsystem within the Kernel enables short-range wireless communication between devices. It allows devices to exchange data and establish connections by utilizing radio frequency identification (RFID) and electromagnetic induction. However, a vulnerability has been identified in the NFC subsystem that can lead to a NULL pointer dereference in the llcp_sock_getname() function after a failed connect operation.
Vulnerability Detail
The vulnerability in the NFC subsystem arises from a NULL pointer dereference in the llcp_sock_getname() function. When a connect operation fails, the function attempts to retrieve the name associated with the socket. However, due to a programming error, it does not properly handle the case where the socket name is NULL. This can result in a NULL pointer dereference, leading to a system crash or potential privilege escalation if an attacker can trigger the vulnerable code path. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v3.3 of the Linux Kernel by commit d646960f7986fefb460a2b062d5ccc8ccfeacc3a and has been fixed in version v4.4.272 by commit eb6875d48590d8e564092e831ff07fa384d7e477.
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 Kernel's NFC subsystem that can lead to a NULL pointer dereference in the llcp_sock_getname() function. This vulnerability can result in a system crash or potential privilege escalation. It is crucial to update the Linux Kernel to version v4.4.272 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from a system crash to potential privilege escalation if an attacker can exploit the vulnerable code path.
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 without requiring access to the code or installation. Simply upload your manifest file (e.g., package-lock.json) to the playground and it will provide information on any vulnerabilities detected.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix or update to mitigate any potential risks.
The exact attack vector and remote exploitability of this vulnerability have not been determined. Further analysis and testing are required to assess the potential for remote exploitation.
If you are unable to update the Kernel immediately, it is recommended to follow general security best practices such as ensuring proper network segmentation, implementing strong access controls, and regularly monitoring system logs for any suspicious activity. However, updating to the latest version of the Kernel is the most effective way to mitigate this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
