Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and timer latency. If the program using this is killed via a SIGTERM, the threads are shutdown one at a time and another tracing instance can start up resetting the threads before they are fully closed. That causes the hrtimer assigned to the kthread to be shutdown and freed twice when the dying thread finally closes the file descriptors, causing a use-after-free bug. Only cancel the hrtimer if the associated thread is still around. Also add the interface_lock around the resetting of the tlat_var->kthread. Note, this is just a quick fix that can be backported to stable. A real fix is to have a better synchronization between the shutdown of old threads and the starting of new ones.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.5, < 6.6.51 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/8a9d0d405159e9c796ddf771f7cff691c1a2bc1ePatch
- https://git.kernel.org/stable/c/8c72f0b2c45f21cb8b00fc37f79f632d7e46c2edPatch
- https://git.kernel.org/stable/c/e6a53481da292d970d1edf0d8831121d1c5e2f0dPatch
FAQ
What is CVE-2024-46845?
CVE-2024-46845 is a vulnerability with a CVSS score of 7.8 (HIGH). In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Only clear timer if a kthread exists The timerlat tracer can use user space threads to check for osnoise and tim...
How severe is CVE-2024-46845?
CVE-2024-46845 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-46845?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.