CVE-2026-98076: Linux kernel · tracing/probes: Fix use-after-free on field name/type of events with multiple probes
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in a2510fcaad92b09b34574c97e8356234c6a84a9a : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in a2510fcaad92b09b34574c97e8356234c6a84a9a, 38305e1b8b1ec27eef8f2d4e461e3b6c8624d494, 9379e193826f23876daccb3351fab89c87084ba3 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available in the Linux kernel as indicated by multiple fixed commit versions. Users should update to a fixed kernel version containing the patches referenced by the commit hashes provided. No additional mitigation is required as the issue is resolved by the official fix.
Description
A use-after-free vulnerability was identified and fixed in the Linux kernel's tracing/probes subsystem affecting events with multiple probes. The issue arises because field name and type strings for probe-based dynamic events were not duplicated but referenced directly, leading to dangling pointers when one of multiple probes is removed. This can cause kernel memory corruption and crashes when accessing freed memory.
References
- git.kernel.org/stable/c/38305e1b8b1ec27eef8f2d4e461e3b6c8624d494 (opens in a new tab)
- git.kernel.org/stable/c/6d6118c17bc791594cbfd9cc4936ee21073b894a (opens in a new tab)
- git.kernel.org/stable/c/a2510fcaad92b09b34574c97e8356234c6a84a9a (opens in a new tab)
- git.kernel.org/stable/c/9379e193826f23876daccb3351fab89c87084ba3 (opens in a new tab)
- git.kernel.org/stable/c/68ae584169c7a41fc9bc4677c1d368983cf44b21 (opens in a new tab)
- git.kernel.org/stable/c/411c9080a776577664531b4f7d3ee53b7a747ba8 (opens in a new tab)
- git.kernel.org/stable/c/178ff2e011e21fbebdf57f5d58a408fe59136d82 (opens in a new tab)
- git.kernel.org/stable/c/86b7a239ec6b14a7544200ede85474c6f5526049 (opens in a new tab)