CVE-2026-99238
tracing: Hold trace_types_lock when updating modules in persistent instances
No exploitation reported by the sources we read.
- Published2026-11-02
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-11-0216:06CVE publishedCNA
Observed activity
isMalicious corpus · updated 2026-11-02 15:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-99238?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-99238?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
Products declared by the CNA
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43, < 57408eac99b0d8a005796346d317d31f0ca4e07afixed in 57408eac99b0d8a005796346d317d31f0ca4e07agit
- ≥ 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43, < dab2bd4d67ad5eaa95019a9511f8d379401b5021fixed in dab2bd4d67ad5eaa95019a9511f8d379401b5021git
- ≥ 5f3719f697c3fdfae5cd6805f10ac7a04b0f4e43, < 244c442f54601a24c86ad90572bf36fc3df41c5efixed in 244c442f54601a24c86ad90572bf36fc3df41c5egit
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 6.15no fix stated
Not affected < 6.15 · ≥ 6.18.60, ≤ 6.18.* · ≥ 7.2.14, ≤ 7.2.* · ≥ 7.3.1, ≤ 7.3.*
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-02
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-99238 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
- Metasploit modules
- none listed Metasploit Framework
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-02
Frequently asked questions
What is CVE-2026-99238?
Is CVE-2026-99238 actively exploited?
What is the CVSS score for CVE-2026-99238?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.