net: netlink: af_netlink: Prevent empty skb by adding a check on len
Summary
GSD-2021-1002611: net: netlink: af_netlink: Prevent empty skb by adding a check on len. Affects Kernel versions < c54a60c8fbaa774f828e26df79f66229a8a0e010. 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 affected package is the Linux Kernel, which is a widely used open-source operating system kernel. It provides the core functionality for various Linux distributions. The netlink subsystem in the kernel allows communication between the kernel and user-space processes. The af_netlink module is responsible for handling netlink sockets. This vulnerability specifically affects the af_netlink module in the kernel.
Vulnerability Detail
The vulnerability in the af_netlink module allows for the creation of an empty skb (socket buffer) without proper length validation. This can lead to various security issues, including potential memory corruption or information disclosure. An attacker could exploit this vulnerability by sending specially crafted netlink messages to the affected system, potentially causing a denial-of-service (DoS) condition or executing arbitrary code with kernel privileges.
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 above by updating the Linux Kernel.
Conclusion
In conclusion, the af_netlink module in the Linux Kernel is vulnerable to an issue that can result in memory corruption, information disclosure, DoS attacks, or arbitrary code execution. It is crucial to update the kernel to version v4.4.296 or later 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 can vary depending on the attacker's capabilities and the system's configuration. It could potentially lead to memory corruption, information disclosure, denial-of-service (DoS) attacks, or arbitrary code execution with kernel privileges.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
The vulnerability is fixed in Linux Kernel version v4.4.296 and later. Versions prior to this may be affected. It is recommended to update to a version that includes the fix.
For more details about this vulnerability, including the specific commit that fixed it, you can refer to the source link provided in the database_specific section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
