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-74636tracing: Fix race between update_event_fields and, event_define_fields

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race between update_event_fields and, event_define_fields The following sequence may leads race between event_define_fields() and update_event_fields(): CPU0 (loads module A) CPU1 (loads module B) =============================== =============================== load_module(A) load_module(B) notifier_call_chain notifier_call_chain trace_module_notify trace_module_notify mutex_lock(&event_mutex) trace_event_update_all() trace_module_add_events(A) down_write(&trace_event_sem) __register_event(call_A) __add_event_to_tracers(call_A) event_define_fields(call_A) for each f: list_for_each_entry(field, list_add(&f->link, &class->fields, link) &class->fields) field = class->fields->next; Where access to the class->fields is not protected by the event_mutex in trace_event_update_all(). This produces the following panic: Unable to handle kernel access ... at virtual address 0000000000000018 pc : update_event_fields+0xf8/0x368 Call trace: update_event_fields+0xf8/0x368 trace_event_update_all+0x7c/0x2b4 trace_module_notify+0x4c/0x1dc notifier_call_chain+0x84/0x168 blocking_notifier_call_chain_robust+0x64/0xd4 load_module+0x10c8/0x123c __arm64_sys_finit_module+0x230/0x31c Fix by taking event_mutex in trace_event_update_all() before trace_event_sem.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 months 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.17% · top 93% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 7c6bd60999f32138e3b73fd97ea11ef47a94de25 – < 4e39f7b4d9d36508c53e89e6cbc640728df870b5
    • affected b3bc8547d3be60898818885f5bf22d0a62e2eb48 – < a30d421468300b1e7b2f233136aeb2db8013f555
    • affected b3bc8547d3be60898818885f5bf22d0a62e2eb48 – < e5f1d301b4bdaa4206db251fdc691f623162b0a8
    • affected b3bc8547d3be60898818885f5bf22d0a62e2eb48 – < fdeb190b0905a6aaed1e5d6adfb8613214748d7d
    • affected b3bc8547d3be60898818885f5bf22d0a62e2eb48 – < ed49684e69f846bf50b5050651ccdb87cfd152c0
    • affected b3bc8547d3be60898818885f5bf22d0a62e2eb48 – < f128740f39ab28d1f4ad5bdd10f3e117eec0c374
    • affected b3bc8547d3be60898818885f5bf22d0a62e2eb48 – < c3730b8373bb5059d735509b9e6a00d7eb337d7c
    • affected 55defdf935fab9f2989a197aae1042c082d9a343
    • affected 0c53a5c80e6e286733381a1d9f255ba4039e2e45
    • affected 5.15.33 – < 5.15.216
    • affected 5.16.19 – < 5.17
    • affected 5.17.2 – < 5.18
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.104 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .