Unknown

CVE-2026-97919 — tracing: Take the reference before publishing the named histogram trigger

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.

Published Sep 25, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.2%

ahead of 9% of scored CVEs · Oct 16, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ e53a8dcd36b9ebc9229450eb594ae20e0b2ae0fd and < b6fb2f5370a9a6aec325ab2db1ca3d1a881499b8≥ 7ab0fc61ce73040f89b12d76a8279995ec283541 and < 2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b≥ 7ab0fc61ce73040f89b12d76a8279995ec283541 and < 91c15cdda6033e2439f5975b938754152f3d6e38≥ 7ab0fc61ce73040f89b12d76a8279995ec283541 and < 0fe23b8eaba0d3372c66b7b31204408da0715edcversion ac7ab38c271ba2edaeb0dc35b200ec13339776aeversion 740dab2338f70d93aa8235db5a9541d846d7b21c≥ 6.12.34 and < 6.12.112≥ 6.6.94 and < 6.7 and 2 more ≥ 6.15.3 and < 6.16version 6.16	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 16, 2026 · 2 reading(s) · max 0.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 25, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

4 on the record

git.kernel.org/stable/c/0fe23b8eaba0d3372c66b7b31204408da0715edc
NIST National Vulnerability Database
git.kernel.org/stable/c/2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b
NIST National Vulnerability Database
git.kernel.org/stable/c/91c15cdda6033e2439f5975b938754152f3d6e38
NIST National Vulnerability Database
git.kernel.org/stable/c/b6fb2f5370a9a6aec325ab2db1ca3d1a881499b8
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 2d
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 2d
Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 3d
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 3d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 3d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 3d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-97919 is "tracing: Take the reference before publishing the named histogram trigger", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.