Race Condition Affecting kernel-uki-virt package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-KERNELUKIVIRT-19249336
- published25 Aug 2026
- disclosed22 Aug 2026
Introduced: 22 Aug 2026
NewCVE-2026-74636 (opens in a new tab)How to fix?
There is no fixed version for Centos:10 kernel-uki-virt.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-uki-virt package and not the kernel-uki-virt package as distributed by Centos.
See How to fix? for Centos:10 relevant fixed versions and status.
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.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2521502
- https://access.redhat.com/security/cve/CVE-2026-74636
- https://git.kernel.org/stable/c/4e39f7b4d9d36508c53e89e6cbc640728df870b5
- https://git.kernel.org/stable/c/a30d421468300b1e7b2f233136aeb2db8013f555
- https://git.kernel.org/stable/c/c3730b8373bb5059d735509b9e6a00d7eb337d7c
- https://git.kernel.org/stable/c/e5f1d301b4bdaa4206db251fdc691f623162b0a8
- https://git.kernel.org/stable/c/ed49684e69f846bf50b5050651ccdb87cfd152c0
- https://git.kernel.org/stable/c/f128740f39ab28d1f4ad5bdd10f3e117eec0c374
- https://git.kernel.org/stable/c/fdeb190b0905a6aaed1e5d6adfb8613214748d7d