CVE-2026-99238: tracing: Hold trace_types_lock when updating modules in persistent instances
Published Nov 2, 2026
·
Updated
In the Linux kernel, the following vulnerability has been resolved:
tracing: Hold tracetypeslock when updating modules in persistent instances
tracemodulerecord() walks ftracetracearrays from the module notifier
without tracetypeslock. A concurrent rmdir of an instance removes it
from the list and frees it under that lock, so a module load or unload
can walk into a freed tracearray.
SecAlerts Pty Ltd. 132 Wickham Terrace Fortitude Valley, QLD 4006, Australia info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
What conditions are required to trigger this issue?
The race requires concurrent activity: a module load or unload invokes the module notifier while a tracing instance is removed with rmdir. The removed instance must be a persistent tracing instance represented in the ftrace_trace_arrays list.
2
Who is realistically exposed?
Systems running an affected listed Ubuntu Linux kernel variant are exposed when they use tracing instances and allow the relevant concurrent module and tracing-instance operations. The CVSS vector indicates local access and low privileges are required; no user interaction is required.
3
What is the impact if the race occurs?
A module load or unload can traverse a trace_array that has been removed and freed, resulting in a use-after-free condition. The supplied severity vector rates confidentiality, integrity, and availability impact as high.