CVE-2026-97919

tracing: Take the reference before publishing the named histogram trigger

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 21, 2026 at 01:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.346.15.36.166.6.94740dab2338f70d93aa8235db5a9541d846d7b21c7ab0fc61ce73040f89b12d76a8279995ec283541ac7ab38c271ba2edaeb0dc35b200ec13339776aee53a8dcd36b9ebc9229450eb594ae20e0b2ae0fd
Vendor states this is fixed in 0fe23b8eaba0d3372c66b7b31204408da0715edc (fixed)
Vendor states this is fixed in 2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b (fixed)
Vendor states this is fixed in 91c15cdda6033e2439f5975b938754152f3d6e38 (fixed)
Vendor states this is fixed in b6fb2f5370a9a6aec325ab2db1ca3d1a881499b8 (fixed)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.16 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card