Vulnerability in Kernel: bpf: Track subprog poke descriptors correctly and fix use-after-free
Summary
GSD-2021-1001154: bpf: Track subprog poke descriptors correctly and fix use-after-free. Affects Kernel versions >= a748c6975dea325da540610c2ba9b5f332c603e6, < 599148d40366bd5d1d504a3a8fcd65e21107e500. 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 manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. This vulnerability specifically affects the bpf (Berkeley Packet Filter) subsystem within the Kernel. The bpf subsystem allows user-defined programs to be executed within the Kernel for packet filtering and network monitoring purposes.
Vulnerability Detail
The vulnerability identified in the bpf subsystem is related to the incorrect tracking of subprogram poke descriptors, leading to a use-after-free issue. This vulnerability was introduced in version v5.10 of the Linux Kernel and was fixed in version v5.13.5. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service (DoS) condition. The use-after-free issue occurs when a program continues to reference memory after it has been freed, potentially leading to memory corruption and unpredictable behavior.
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
The vulnerability in the Kernel's bpf subsystem, which incorrectly tracks subprogram poke descriptors and leads to a use-after-free issue, has been identified and fixed in version v5.13.5. It is crucial to update the Kernel to the fixed version to mitigate the potential risks associated with this vulnerability. For further support and assistance in vulnerability remediation, please 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. However, it could potentially allow an attacker to execute arbitrary code within the Kernel or cause a denial-of-service (DoS) condition.
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 to the playground, and it will analyze the dependencies and alert you if any open-source vulnerabilities, including this one, are detected.
At the time of this report, there are no known public exploits available for this vulnerability. However, it is always recommended to apply security patches promptly to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely if the attacker can send malicious packets to the affected system or if the system is exposed to untrusted network traffic.
In addition to updating the Kernel to the fixed version, it is recommended to follow general security best practices such as implementing proper network segmentation, using firewalls, and regularly monitoring and patching the system for any security updates.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
