CVE-2026-99237: tracing: Hold trace_types_lock when resetting last boot data from readers
Published Nov 2, 2026
·
Updated
In the Linux kernel, the following vulnerability has been resolved:
tracing: Hold tracetypeslock when resetting last boot data from readers
updatelastdataifempty() is called from tracingopen() with OTRUNC,
tracingreadpipe() and tracingbuffersread() without tracetypeslock.
Two readers can both pass the LASTBOOT test and free moduledelta
twice, and a module notifier can update moduledelta while it is being
freed.
Take tracetypeslock in those paths and keep the callers that already
hold it on an unlocked variant.
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.
The issue involves concurrent readers resetting last-boot tracing data. Relevant paths include opening tracing with O_TRUNC, reading trace_pipe, and reading tracing buffers; a module notifier updating module_delta concurrently can also race with its cleanup.
2
What is the likely impact if the race occurs?
Two readers can both pass the LAST_BOOT check and free module_delta twice. A module notifier may also update module_delta while it is being freed, creating a use-after-free or double-free condition with high confidentiality, integrity, and availability impact.
3
Which Ubuntu kernel packages are listed as affected?
The listed software includes ubuntu/linux, ubuntu/linux-fips, ubuntu/linux-aws, ubuntu/linux-azure, ubuntu/linux-gcp, ubuntu/linux-oracle, ubuntu/linux-aws-fips, and ubuntu/linux-azure-fips.