tracing: Hold trace_types_lock when updating modules in persistent instances
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A concurrent rmdir of a tracing instance while a module is loaded or unloaded
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: tracing: Hold trace_types_lock when updating modules in persistent instances trace_module_record() walks ftrace_trace_arrays from the module notifier without trace_types_lock. 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 trace_array.
What to do
Check whether your setup matches what the bug needs.
A concurrent rmdir of a tracing instance while a module is loaded or unloadedWorkaround: The checked facts record no fix and no workaround. The only trigger they describe is removing a tracing instance with rmdir while a module is loaded or unloaded.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
6.15
Evidence 3
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-99238
What does this mean?
A module load or unload can access a freed trace_array in the kernel, a use-after-free. This happens when a tracing instance is removed with rmdir at the same time.Source: git.kernel.org
Am I affected, and how do I check?
The checked facts list no affected version ranges. The described trigger is a concurrent rmdir of a tracing instance while a module is loaded or unloaded, so compare your kernel version with the version ranges in the advisory.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts record no fix and no workaround. The only trigger they describe is removing a tracing instance with rmdir while a module is loaded or unloaded.Source: git.kernel.org