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-97924tracing/user_events: Don't destroy fields when event removal fails

Description

In the Linux kernel, the following vulnerability has been resolved: tracing/user_events: Don't destroy fields when event removal fails destroy_user_event() destroys the event's fields before attempting to remove the trace event call. If user_event_set_call_visible() fails, e.g. because the event is still enabled and trace_remove_event_call() returns -EBUSY, the event is left registered with an irreversibly destroyed field list. Any subsequent interaction with the event then operates on an empty field list while it is still fully visible in tracefs. Move the field destruction after the call removal, and splice the field list back onto the event when the removal fails so the event remains in a consistent state.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 35 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 (18 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 7f5a08c79df35e68f1a43033450c5050f12bc155 – < c8efcb80f0b4d253482f9117db29bb92b4197d52
    • affected 7f5a08c79df35e68f1a43033450c5050f12bc155 – < a3d9b8b7c8f3627976fe758c77ffd3da260824d7
    • affected 7f5a08c79df35e68f1a43033450c5050f12bc155 – < 9c62b7e92b6086a2a0aeb71f3553dd8cf7fdcd8b
    • affected 7f5a08c79df35e68f1a43033450c5050f12bc155 – < 0892da2272ec565858aa1ec5458552d699de9142
    • affected 7f5a08c79df35e68f1a43033450c5050f12bc155 – < 62d6544e86506bb0695c9594c713cba859666f2f
    • affected 7f5a08c79df35e68f1a43033450c5050f12bc155 – < 2deb753127d7b7035e893955c5e91875e767d1f8
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .