Vulnerability in Kernel package: nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect
Summary
UVI-2021-1000726: nfc: fix NULL ptr dereference in llcp_sock_getname() after failed connect. Affects Kernel versions >= d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 39c15bd2e5d11bcf7f4c3dba2aad9e1e110a5d94. 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 package is a crucial component of the Linux operating system. It provides the core functionality and acts as an interface between the hardware and software layers. The nfc subsystem within the Kernel package enables Near Field Communication (NFC) capabilities, allowing devices to communicate over short distances. This vulnerability specifically affects the llcp_sock_getname() function within the nfc subsystem.
Vulnerability Detail
The vulnerability arises from a NULL pointer dereference in the llcp_sock_getname() function after a failed connect operation. This can be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with kernel privileges. The vulnerability was introduced in version v3.3 of the Linux Kernel and is fixed in version v4.9.272.
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 known workaround for this vulnerability. It is essential to apply the fix mentioned above to ensure the security and stability of the system.
Conclusion
The vulnerability in the Kernel package, specifically in the nfc subsystem's llcp_sock_getname() function, can lead to a denial-of-service condition or potential execution of arbitrary code with kernel privileges. It is crucial to update the Linux Kernel package to version v4.9.272 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to a denial-of-service (DoS) condition or potential execution of arbitrary code with kernel privileges.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the Vulert Playground will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the fix as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to untrusted network connections.
An attacker would need to have the ability to send crafted network packets to the vulnerable system in order to exploit this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
