Not yet scoredPublished Aug 22, 2026

CVE-2026-74636tracing: Fix race between update_event_fields and, event_define_fields

Updated under an hour ago (Oct 27, 2026, 9:23 PM ET)

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: Not yet scored
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Received
Record last updated: Aug 22, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	7c6bd60999f32138e3b73fd97ea11ef47a94de25 builds before 4e39f7b4d9d36508c53e89e6cbc640728df870b5; from b3bc8547d3be60898818885f5bf22d0a62e2eb48 before a30d421468300b1e7b2f233136aeb2db8013f555; from b3bc8547d3be60898818885f5bf22d0a62e2eb48 before e5f1d301b4bdaa4206db251fdc691f623162b0a8; from b3bc8547d3be60898818885f5bf22d0a62e2eb48 before fdeb190b0905a6aaed1e5d6adfb8613214748d7d; from b3bc8547d3be60898818885f5bf22d0a62e2eb48 before ed49684e69f846bf50b5050651ccdb87cfd152c0; from b3bc8547d3be60898818885f5bf22d0a62e2eb48 before f128740f39ab28d1f4ad5bdd10f3e117eec0c374; from b3bc8547d3be60898818885f5bf22d0a62e2eb48 before c3730b8373bb5059d735509b9e6a00d7eb337d7c; 55defdf935fab9f2989a197aae1042c082d9a343; and 4 more ranges	CNA record

References

References

https://git.kernel.org/stable/c/4e39f7b4d9d36508c53e89e6cbc640728df870b5
https://git.kernel.org/stable/c/a30d421468300b1e7b2f233136aeb2db8013f555
https://git.kernel.org/stable/c/e5f1d301b4bdaa4206db251fdc691f623162b0a8
https://git.kernel.org/stable/c/fdeb190b0905a6aaed1e5d6adfb8613214748d7d
https://git.kernel.org/stable/c/ed49684e69f846bf50b5050651ccdb87cfd152c0
https://git.kernel.org/stable/c/f128740f39ab28d1f4ad5bdd10f3e117eec0c374
https://git.kernel.org/stable/c/c3730b8373bb5059d735509b9e6a00d7eb337d7c

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.