Answer in brief
CVE-2025-37845 records a High severity (CVSS 7.8) vulnerability in tracing: fprobe events: Fix possible UAF on modules. 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.
CVSS is 7.8. 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 | >=71c9cf87776eaa556fc0a0a060df94200e1f521c <868df4eb784c3ccc7e4340a9ea993cbbedca167e || >=9db2b8cf4ea07b579db588e0353d5680f5d1f071 <a27d2de2472b1cc7d582ab405d1d5832a80481de || >=ac91052f0ae5be9e46211ba92cc31c0e3b0a933a <626f01f4d26e8cf92e69c1df53036153c8e98a20 || >=ac91052f0ae5be9e46211ba92cc31c0e3b0a933a <dd941507a9486252d6fcf11814387666792020f3 || >=6.12.21 <6.12.24 || >=6.13.9 <6.13.12 | 868df4eb784c3ccc7e4340a9ea993cbbedca167e, a27d2de2472b1cc7d582ab405d1d5832a80481de, 626f01f4d26e8cf92e69c1df53036153c8e98a20, dd941507a9486252d6fcf11814387666792020f3, 6.12.24, 6.13.12 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
May 9, 2025
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: fprobe events: Fix possible UAF on modules Commit ac91052f0ae5 ("tracing: tprobe-events: Fix leakage of module refcount") moved try_module_get() from __find_tracepoint_module_cb() to find_tracepoint() caller, but that introduced a possible UAF because the module can be unloaded before try_module_get(). In this case, the module object should be freed too. Thus, try_module_get() does not only fail but may access to the freed object. To avoid that, try_module_get() in __find_tracepoint_module_cb() again.
Quoted source text, attributed separately from HOL analysis.