NULL ptr dereference in llcp_sock_getname() after failed connect in Kernel
Summary
GSD-2021-1000780: nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect. Affects Kernel versions >= d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 48ee0db61c8299022ec88c79ad137f290196cac2. 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 functionality and acts as a bridge 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 vulnerability in question affects the Kernel's NFC (Near Field Communication) subsystem, which enables communication between devices in close proximity.
Vulnerability Detail
The vulnerability arises from a NULL pointer dereference in the llcp_sock_getname() function after a failed connect operation in the NFC subsystem. This issue can be exploited by an attacker to cause a denial-of-service condition or potentially execute arbitrary code with kernel privileges. The vulnerability was introduced in version v3.3 of the Linux Kernel and has been fixed in version v5.10.43.
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
If updating the Kernel is not immediately feasible, a possible workaround is to disable the NFC subsystem or restrict its usage to trusted devices only. This can be achieved by modifying the system configuration or using kernel command-line parameters. However, it is important to note that workarounds may have limitations and it is still recommended to apply the official fix as soon as possible.
Conclusion
The NULL pointer dereference vulnerability in llcp_sock_getname() in the Kernel's NFC subsystem can have serious security implications, potentially leading to a denial-of-service condition or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.10.43 or later to mitigate this vulnerability. If immediate updating is not possible, consider applying the provided workaround or taking additional security measures. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service condition or potential execution of arbitrary code with kernel privileges, allowing an attacker to compromise the affected system.
You can use the Vulert playground (https://vulert.com/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.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the fix or workaround as soon as possible to mitigate any potential risk.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is crucial to apply the necessary patches or updates to prevent any potential attacks.
To exploit this vulnerability, an attacker would need network access to the affected system and the ability to send specially crafted NFC packets. However, the exact prerequisites may vary depending on the specific configuration and environment.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
