CVE-2026-99233tracing/histograms: Verify event_call identity when updating synth_event refcount
- 7.8HighCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Verify event_call identity when updating synth_event refcount In event_hist_trigger_parse() and hist_unreg_all(), the histogram registration and unregistration paths look up find_synth_event() using trace_event_name(file->event_call) and adjust se->ref if a match is found. Because find_synth_event() only compares the event basename, registering or removing a histogram on a non-synthetic trace event whose basename matches a synthetic event erroneously modifies the synthetic event's reference count. If a histogram is registered on the non-synthetic event before the synthetic event is created and removed afterwards, se->ref is decremented without a matching increment, allowing the synthetic event to be freed while an active histogram action still holds a pointer to it. Introduce find_synth_event_call() to verify that &se->call matches file->event_call before adjusting se->ref.
Timeline
ID reserved
By Linux
- 38 days later
· 38 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < 381f543ed35c434d5b707369aa5dcd69ecf440af
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < 4472579bd1c83708b6fe623c870cdf728e947205
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < 23b4106e8b35823acc79e206c7745f55b9cfd78b
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < 06e816bed499fe47f39f12044382cc5d064485fb
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < 5597bb8db6855fcb97a67196d227fea359bcd81c
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < cf4e31d5da80fae4c9cdbe7af55b7c3ad213f0e4
- affected 4b147936fa509650beaf638b331573c23ba4d609 – < 3403d9bb27ebc3572bd048620746b4414e073bf9
- affected 4.17
- unaffected < 4.17
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.60 – ≤ 6.18.*
- unaffected 7.2.14 – ≤ 7.2.*
- unaffected 7.3.1 – ≤ 7.3.*
- unaffected 7.4-rc1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/381f543ed35c434d5b707369aa5dcd69ecf440af (opens in a new tab)
- https://git.kernel.org/stable/c/4472579bd1c83708b6fe623c870cdf728e947205 (opens in a new tab)
- https://git.kernel.org/stable/c/23b4106e8b35823acc79e206c7745f55b9cfd78b (opens in a new tab)
- https://git.kernel.org/stable/c/06e816bed499fe47f39f12044382cc5d064485fb (opens in a new tab)
- https://git.kernel.org/stable/c/5597bb8db6855fcb97a67196d227fea359bcd81c (opens in a new tab)
- https://git.kernel.org/stable/c/cf4e31d5da80fae4c9cdbe7af55b7c3ad213f0e4 (opens in a new tab)
- https://git.kernel.org/stable/c/3403d9bb27ebc3572bd048620746b4414e073bf9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-115275 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99233)Record last updated .