CVE-2026-98415: Linux kernel · soc: samsung: exynos-pmu: fix use-after-free of interrupt generator node
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 4450102d6aa2a85b1d2d8610920fcbe45eb0ef69 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4450102d6aa2a85b1d2d8610920fcbe45eb0ef69, 164313e24cb0f51528bc2099c5564174ead11d8a, 4dd1999783d7d12434006289338373e49492dc96
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 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 Linux kernel to 4450102d6aa2a85b1d2d8610920fcbe45eb0ef69, 164313e24cb0f51528bc2099c5564174ead11d8a or 4dd1999783d7d12434006289338373e49492dc96.
Affected software
| Product | 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 and has been applied in the Linux kernel. Users should update to the fixed kernel versions identified by the commit hashes provided. No additional mitigation is required beyond applying the official patch.
Description
A use-after-free vulnerability was identified and fixed in the Linux kernel's Samsung Exynos PMU driver. The issue involved improper handling of the interrupt generator node's reference count, leading to a use-after-free condition. This was corrected by changing the node's declaration and removing an erroneous reference count decrement.