Answer in brief
CVE-2024-46845 records a Unknown severity vulnerability in tracing/timerlat: Only clear timer if a kthread exists. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e88ed227f639ebcb31ed4e5b88756b47d904584b <8c72f0b2c45f21cb8b00fc37f79f632d7e46c2ed || >=e88ed227f639ebcb31ed4e5b88756b47d904584b <8a9d0d405159e9c796ddf771f7cff691c1a2bc1e || >=e88ed227f639ebcb31ed4e5b88756b47d904584b <e6a53481da292d970d1edf0d8831121d1c5e2f0d | 8c72f0b2c45f21cb8b00fc37f79f632d7e46c2ed, 8a9d0d405159e9c796ddf771f7cff691c1a2bc1e, e6a53481da292d970d1edf0d8831121d1c5e2f0d |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
Sep 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-46845 records a Unknown severity vulnerability in tracing/timerlat: Only clear timer if a kthread exists. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e88ed227f639ebcb31ed4e5b88756b47d904584b <8c72f0b2c45f21cb8b00fc37f79f632d7e46c2ed || >=e88ed227f639ebcb31ed4e5b88756b47d904584b <8a9d0d405159e9c796ddf771f7cff691c1a2bc1e || >=e88ed227f639ebcb31ed4e5b88756b47d904584b <e6a53481da292d970d1edf0d8831121d1c5e2f0d | 8c72f0b2c45f21cb8b00fc37f79f632d7e46c2ed, 8a9d0d405159e9c796ddf771f7cff691c1a2bc1e, e6a53481da292d970d1edf0d8831121d1c5e2f0d |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
Sep 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.