Answer in brief
CVE-2026-97919 records a Unknown severity vulnerability in tracing: Take the reference before publishing the named histogram trigger. 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 | >=7ab0fc61ce73040f89b12d76a8279995ec283541 <2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b || >=7ab0fc61ce73040f89b12d76a8279995ec283541 <91c15cdda6033e2439f5975b938754152f3d6e38 || >=7ab0fc61ce73040f89b12d76a8279995ec283541 <0fe23b8eaba0d3372c66b7b31204408da0715edc || ac7ab38c271ba2edaeb0dc35b200ec13339776ae || e53a8dcd36b9ebc9229450eb594ae20e0b2ae0fd || 740dab2338f70d93aa8235db5a9541d846d7b21c || >=6.6.94 <6.7 || >=6.12.34 <6.13 || >=6.15.3 <6.16 | 2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b, 91c15cdda6033e2439f5975b938754152f3d6e38, 0fe23b8eaba0d3372c66b7b31204408da0715edc, 6.7, 6.13, 6.16 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it shares its histogram with: data->ref++; save_named_trigger(data->named_data->name, data); ret = event_hist_trigger_init(data->named_data); if (ret < 0) { kfree(data->cmd_ops); data->cmd_ops = &trigger_hist_cmd; } return ret; event_hist_trigger_init() fails when alloc_hist_pad() cannot allocate, and nothing takes the trigger back off the list on the way out. event_hist_trigger_parse() frees it, and the next lookup by name reads the freed object: BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0 Read of size 8 at addr ffff888009346860 by task init/1 find_named_trigger+0xac/0xc0 hist_register_trigger+0xc1/0xa00 event_hist_trigger_parse+0x3146/0x6af0 event_trigger_write+0xce/0x160 Freed by task 67: kfree+0x154/0x420 trigger_kthread_fn+0xfd/0x160 Do the reference first and publish once it has succeeded, so that nothing which can fail runs after the trigger becomes findable.
Quoted source text, attributed separately from HOL analysis.