In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race between update_event_fields and, event_define_fields The… (CVE-2026-74636)
A race condition vulnerability in the Linux kernel tracing subsystem has been resolved. The flaw occurs due to unsynchronized access to the class->fields list between event_define_fields() and update_event_fields() functions during module loading. This race can lead to a kernel panic caused by invalid memory access. The fix involves acquiring the event_mutex lock in trace_event_update_all() to properly synchronize access.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel tracing subsystem arises from a race condition between event_define_fields() and update_event_fields() functions. When two CPUs concurrently load different kernel modules, unsynchronized access to the class->fields linked list can occur because event_mutex is not held in trace_event_update_all(). This leads to a kernel panic with an invalid memory access at a null pointer offset. The issue is fixed by taking the event_mutex lock in trace_event_update_all() before acquiring trace_event_sem, ensuring proper synchronization and preventing the race.
Potential Impact
Exploitation of this race condition can cause a kernel panic, resulting in a denial of service by crashing the system. There is no indication of privilege escalation or arbitrary code execution from the provided information.
Mitigation Recommendations
A fix has been implemented that takes the event_mutex lock in trace_event_update_all() before trace_event_sem to prevent the race condition. Users should apply the official Linux kernel update that includes this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix race between update_event_fields and, event_define_fields The… (CVE-2026-74636)
Description
A race condition vulnerability in the Linux kernel tracing subsystem has been resolved. The flaw occurs due to unsynchronized access to the class->fields list between event_define_fields() and update_event_fields() functions during module loading. This race can lead to a kernel panic caused by invalid memory access. The fix involves acquiring the event_mutex lock in trace_event_update_all() to properly synchronize access.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel tracing subsystem arises from a race condition between event_define_fields() and update_event_fields() functions. When two CPUs concurrently load different kernel modules, unsynchronized access to the class->fields linked list can occur because event_mutex is not held in trace_event_update_all(). This leads to a kernel panic with an invalid memory access at a null pointer offset. The issue is fixed by taking the event_mutex lock in trace_event_update_all() before acquiring trace_event_sem, ensuring proper synchronization and preventing the race.
Potential Impact
Exploitation of this race condition can cause a kernel panic, resulting in a denial of service by crashing the system. There is no indication of privilege escalation or arbitrary code execution from the provided information.
Mitigation Recommendations
A fix has been implemented that takes the event_mutex lock in trace_event_update_all() before trace_event_sem to prevent the race condition. Users should apply the official Linux kernel update that includes this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jcq2-873m-mp53
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74636"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f2acd9273b499bc80e
Added to database: 08/22/2026, 22:51:30 UTC
Last enriched: 08/22/2026, 23:52:49 UTC
Last updated: 08/23/2026, 00:32:10 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.