Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ac7ab38c271ba2edaeb0dc35b200ec13339776ae – < e5c5dad169fb569161d3eed6c3f6a59e65db1830
    • affected e53a8dcd36b9ebc9229450eb594ae20e0b2ae0fd – < b6fb2f5370a9a6aec325ab2db1ca3d1a881499b8
    • affected 7ab0fc61ce73040f89b12d76a8279995ec283541 – < 2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b
    • affected 7ab0fc61ce73040f89b12d76a8279995ec283541 – < 91c15cdda6033e2439f5975b938754152f3d6e38
    • affected 7ab0fc61ce73040f89b12d76a8279995ec283541 – < 0fe23b8eaba0d3372c66b7b31204408da0715edc
    • affected 740dab2338f70d93aa8235db5a9541d846d7b21c
    • affected 6.6.94 – < 6.6.160
    • affected 6.12.34 – < 6.12.112
    • affected 6.15.3 – < 6.16
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97919 badge
[![CVE-2026-97919](https://cveledger.app/badge/CVE-2026-97919.svg)](https://cveledger.app/cve/CVE-2026-97919)

Record last updated .