net: netlink: af_netlink: Prevent empty skb by adding a check on len
Summary
GSD-2021-1002633: net: netlink: af_netlink: Prevent empty skb by adding a check on len. Affects Kernel versions < 54e785f7d5c197bc06dbb8053700df7e2a093ced. 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 Linux Kernel is an open-source monolithic Unix-like computer operating system kernel. It provides the core functionality for the Linux operating system. The netlink subsystem is a kernel interface used for communication between the kernel and user-space processes. The af_netlink module is responsible for handling netlink sockets. These sockets are used for various networking-related operations. The vulnerability in the af_netlink module allows for the creation of an empty skb (socket buffer) without proper checks on its length.
Vulnerability Detail
The vulnerability in the af_netlink module allows an attacker to create an empty skb without proper checks on its length. This can lead to various security issues, such as kernel crashes, privilege escalation, or information leaks. By exploiting this vulnerability, an attacker could potentially execute arbitrary code with kernel-level privileges. The vulnerability was fixed in Linux Kernel version v4.14.259 by commit 54e785f7d5c197bc06dbb8053700df7e2a093ced.
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 recommended to apply the fix mentioned in the 'how_to_fix' section.
Conclusion
The vulnerability in the af_netlink module of the Linux Kernel allows for the creation of an empty skb without proper checks on its length. This can lead to various security issues, including kernel crashes, privilege escalation, and information leaks. It is crucial to update the Linux Kernel to version v4.14.259 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can range from kernel crashes to privilege escalation and information leaks. An attacker could potentially execute arbitrary code with kernel-level privileges.
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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
At the time of writing, there is no known public exploit for this vulnerability. However, it is always recommended to apply security patches and updates as soon as they become available.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to untrusted network traffic. It is important to apply the necessary security measures and keep the system up to date to mitigate the risk.
The only known mitigation for this vulnerability is to update the Linux Kernel to version v4.14.259 or later. It is recommended to follow the steps mentioned in the 'how_to_fix' section to apply the necessary fix.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
