tracing/timerlat: Only clear timer if a kthread exists
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.516.10.106.11In 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.
From the CVE record · Linux
The Linux kernel's timerlat tracer has a use-after-free vulnerability involving its hrtimer. If a program using timerlat user-space threads is terminated with SIGTERM, another tracing instance can start before those threads finish shutting down, causing the timer to be freed twice. This requires local interaction with the tracer; the input does not specify an authentication requirement.
Engineers running Linux kernels that use the timerlat tracer should check their kernel versions; affected versions were not provided.