Double Uncharge Memory Vulnerability in Kernel
Summary
GSD-2022-1002239: bpf, sockmap: Fix double uncharge the mem of sk_msg. Affects Kernel versions >= 604326b41a6fb9b4a78b6179335decee0365cd8c, < 94c6ac22abcdede72bfaa0f4c22fb370891f4002. 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 functionalities and acts as a bridge between hardware and software. It manages system resources, facilitates communication between processes, and handles various low-level operations. The vulnerability in question affects the Kernel's bpf and sockmap modules, which are responsible for implementing Berkeley Packet Filters and socket-based packet processing, respectively.
Vulnerability Detail
The double uncharge memory vulnerability in the bpf and sockmap modules of the Kernel allows an attacker to exploit a flaw in the handling of sk_msg objects. By manipulating certain parameters, an attacker can cause the system to improperly release memory, leading to a double free condition. This can result in memory corruption, potentially allowing the attacker to execute arbitrary code or crash the system. The vulnerability was introduced in Kernel version 4.20 and is fixed in version 5.4.189.
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
No specific workaround has been mentioned for this vulnerability.
Conclusion
The double uncharge memory vulnerability in the Kernel's bpf and sockmap modules can potentially lead to memory corruption and arbitrary code execution. It is crucial to update the Linux Kernel to version 5.4.189 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow an attacker to execute arbitrary code or crash the system by exploiting memory corruption.
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 analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.
Yes, the vulnerability was introduced in Kernel version 4.20 and affects all versions up to and including version 5.4.188.
For more details about this vulnerability, including technical specifics and the fix commit, you can refer to the vulnerability report at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002239.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
