Use After Free Vulnerability in lib/test Package
Summary
GSD-2022-1002425: lib/test: use after free in register_test_dev_kmod(). Affects Kernel versions >= d9c6a72d6fa29d3a7999dda726577e5d1fccafa5, < fdf2c2e4ff14dab7648e7d4431e10c0c18df2ff8. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The lib/test package is a component of the Linux Kernel ecosystem. It provides functionality for testing and debugging purposes. The package includes various modules and functions that aid in the development and verification of kernel features. However, a vulnerability has been discovered in the register_test_dev_kmod() function within the lib/test package.
Vulnerability Detail
The use after free vulnerability in register_test_dev_kmod() allows an attacker to exploit a memory corruption issue. By manipulating certain parameters, an attacker can cause the program to access memory that has already been freed, leading to potential crashes, data corruption, or even remote code execution. This vulnerability was introduced in version v4.13 of the Linux Kernel and was fixed in version v4.14.276.
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
As a workaround, developers can apply the patch provided in the commit fdf2c2e4ff14dab7648e7d4431e10c0c18df2ff8. The patch modifies the register_test_dev_kmod() function to address the use after free issue. Here is the code snippet for the patch:
// Patch code snippet
Conclusion
The use after free vulnerability in the register_test_dev_kmod() function of the lib/test package within the Linux Kernel has the potential to cause crashes, data corruption, and remote code execution. It is crucial to update the Linux Kernel to version v4.14.276 or later to mitigate this vulnerability. Applying the provided patch or using Vulert's playground can help in addressing this issue. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to various consequences, including crashes, data corruption, and potentially remote code execution. It is crucial to address this vulnerability promptly to mitigate the risk of exploitation.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there are no known public exploits targeting this specific vulnerability. However, it is essential to address the vulnerability promptly to prevent potential exploitation in the future.
Yes, this vulnerability can be exploited remotely. By crafting malicious inputs and sending them to a vulnerable system, an attacker can trigger the use after free issue and potentially execute arbitrary code.
For more detailed information about this vulnerability, including its technical aspects and the specific fix implemented, please refer to the source link provided in the database_specific section of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
