CVE-2026-99237
Received Received - Intake

Race Condition in Linux Kernel Tracing Subsystem

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when resetting last boot data from readers update_last_data_if_empty() is called from tracing_open() with O_TRUNC, tracing_read_pipe() and tracing_buffers_read() without trace_types_lock. Two readers can both pass the LAST_BOOT test and free module_delta twice, and a module notifier can update module_delta while it is being freed. Take trace_types_lock in those paths and keep the callers that already hold it on an unlocked variant.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD
CVE-2026-99237

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
Linux Linux 32dc0042528d385d83bf458e4cf3a49c5110afea
Linux Linux 32dc0042528d385d83bf458e4cf3a49c5110afea
Linux Linux 32dc0042528d385d83bf458e4cf3a49c5110afea
Linux Linux 6.16

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Linux kernel vulnerability where a race condition occurs in the tracing subsystem. The issue involves the update_last_data_if_empty() function being called without proper locking, allowing two readers to free memory twice and a module notifier to update freed memory. The fix requires holding the trace_types_lock during these operations.

Detection Guidance

This vulnerability is specific to the Linux kernel's tracing subsystem. Detection requires checking the kernel version and tracing-related components. Use commands like 'uname -r' to check the kernel version and 'lsmod | grep trace' to verify tracing modules. If the kernel version is vulnerable, inspect tracing operations for race conditions or double-free issues in module_delta handling.

Impact Analysis

This vulnerability could lead to system crashes, data corruption, or privilege escalation. An attacker with local access might exploit it to execute arbitrary code, gain elevated privileges, or cause denial-of-service conditions on affected systems.

Compliance Impact

This vulnerability in the Linux kernel involves improper handling of trace data, leading to potential memory corruption and double-free issues. While it does not directly impact data privacy or security controls required by standards like GDPR or HIPAA, it could indirectly affect compliance by compromising system stability and integrity, which are foundational for maintaining secure environments.

Mitigation Strategies

Immediately update the Linux kernel to a patched version where this issue is resolved. If updating is not immediately possible, disable the tracing subsystem by removing or blacklisting the 'trace' kernel module. Monitor system logs for signs of exploitation or crashes related to tracing operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-99237. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...