CVE-2026-74636

CVE CVE-2026-74636EUVD EUVD-2026-64573Published 2026-08-22T15:32:16.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux b3bc8547d3be60898818885f5bf22d0a62e2eb48 <f128740f39ab28d1f4ad5bdd10f3e117eec0c374; 7c6bd60999f32138e3b73fd97ea11ef47a94de25 <4e39f7b4d9d36508c53e89e6cbc640728df870b5; 5.18; 5.17.2 <5.18; patch: 0; patch: 6.6.152; b3bc8547d3be60898818885f5bf22d0a62e2eb48 <e5f1d301b4bdaa4206db251fdc691f623162b0a8; b3bc8547d3be60898818885f5bf22d0a62e2eb48 <c3730b8373bb5059d735509b9e6a00d7eb337d7c; b3bc8547d3be60898818885f5bf22d0a62e2eb48 <fdeb190b0905a6aaed1e5d6adfb8613214748d7d; 5.16.19 <5.17; patch: 6.18.45; 0c53a5c80e6e286733381a1d9f255ba4039e2e45; 5.15.33 <5.15.216; patch: 6.1.183; b3bc8547d3be60898818885f5bf22d0a62e2eb48 <ed49684e69f846bf50b5050651ccdb87cfd152c0; patch: 5.15.216; patch: 7.1.9; patch: 7.2; 55defdf935fab9f2989a197aae1042c082d9a343; patch: 6.12.104; b3bc8547d3be60898818885f5bf22d0a62e2eb48 <a30d421468300b1e7b2f233136aeb2db8013f555

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.