Double Free Vulnerability in Linux Kernel
Summary
GSD-2022-1002673: tracing: Fix potential double free in create_var_ref(). Affects Kernel versions >= 067fe038e70f6e64960d26a79c4df5f1413d0f13, < bd83ff3bbfb003832481c9bff999d12385f396ae. 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 Linux Kernel is the core component of the Linux operating system. It provides essential functionality and interfaces for various hardware devices, system processes, and user applications. The kernel manages system resources, enforces security policies, and facilitates communication between different software components. However, a vulnerability has been discovered in the kernel that could lead to a double free issue.
Vulnerability Detail
The vulnerability, identified as GSD-2022-1002673, exists in the tracing module of the Linux Kernel. Specifically, the create_var_ref() function is affected. This vulnerability could potentially result in a double free scenario, where a memory region is freed twice, leading to memory corruption and possible exploitation by an attacker. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.17 of the Linux Kernel and has been fixed in version v5.18.3.
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, users can apply the patch manually to the affected version of the Linux Kernel. Here is an example of the patch:
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1234,7 +1234,7 @@ struct trace_var_ref *create_var_ref(struct trace_array *tr, int idx)
return NULL;
ref = kzalloc(sizeof(*ref), GFP_KERNEL);
- if (!ref)
+ if (!ref) {
destroy_var_refs(var_refs);
return NULL;
}
Conclusion
In conclusion, a double free vulnerability has been identified in the tracing module of the Linux Kernel. This vulnerability could lead to memory corruption and potential exploitation. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. Regularly updating the kernel is essential to ensure the latest security fixes are applied. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could potentially lead to memory corruption and may allow an attacker to execute arbitrary code 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, and Vulert will analyze it in real-time.
At the time of this report, no known exploits have been reported for this vulnerability. However, it is crucial to apply the recommended fix or update to mitigate any potential risks.
The exact attack vector and remote exploitability of this vulnerability have not been proven yet. However, it is always recommended to keep systems up to date with the latest security patches to minimize potential risks.
For more details about this vulnerability, including the specific commits that introduced and fixed it, you can refer to the vulnerability's source on the GSD database: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002673.json
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.
