Use After Free Affecting kernel-abi-whitelists package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS7-KERNELABIWHITELISTS-8114667
- published 28 Sep 2024
- disclosed 27 Sep 2024
Introduced: 27 Sep 2024
CVE-2024-46845 Open this link in a new tabHow to fix?
There is no fixed version for Centos:7
kernel-abi-whitelists
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-abi-whitelists
package and not the kernel-abi-whitelists
package as distributed by Centos
.
See How to fix?
for Centos:7
relevant fixed versions and status.
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.