CVE-2026-99237
tracing: Hold trace_types_lock when resetting last boot data from readers
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 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.
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-99237?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-99237?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- ≥ 32dc0042528d385d83bf458e4cf3a49c5110afea, < 92b69f6db640dadc0851762ee2e12db99f083cadfixed in 92b69f6db640dadc0851762ee2e12db99f083cadgit
- ≥ 32dc0042528d385d83bf458e4cf3a49c5110afea, < d6d991afe775ab7fcf89523a2502b7ca3be56ffdfixed in d6d991afe775ab7fcf89523a2502b7ca3be56ffdgit
- ≥ 32dc0042528d385d83bf458e4cf3a49c5110afea, < 1f06cfe0b60a878619d1d8efe1cd0f515b7dc2aafixed in 1f06cfe0b60a878619d1d8efe1cd0f515b7dc2aagit
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 6.16no fix stated
Not affected < 6.16 · ≥ 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-99237 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-99237?
Is CVE-2026-99237 actively exploited?
What is the CVSS score for CVE-2026-99237?
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.