CVE-2026-98721: Linux kernel · mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ
Source GCVE Database
Not known to be exploited · fixed in c69d8aceda362c95bbc4e2182f5829275a7db0c8 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c69d8aceda362c95bbc4e2182f5829275a7db0c8, bbd87eca5407288f2b63ff9357c611cd57e7e640, 24319f25b641e55f84e55455092a39a2485c78d4 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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 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
The vulnerability has been resolved by initializing the IRQ lock and completion object before registering the IRQ handler. Users should apply the official Linux kernel update that includes this fix. Patch status is not explicitly confirmed in the provided data; check the vendor advisory or Linux kernel release notes for the exact fixed versions and update accordingly.
Description
A vulnerability in the Linux kernel's Cadence NAND interrupt handler was resolved by initializing the IRQ state before requesting the IRQ. The issue involved a race condition where the interrupt handler could access uninitialized synchronization state due to the IRQ being registered before the IRQ lock and completion object were initialized.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98721 (opens in a new tab)
- git.kernel.org/stable/c/1ed0ccd5649154bfc00ab11c59262d4f42515252 (opens in a new tab)
- git.kernel.org/stable/c/21f027016b1290d13c30b198ae7a00e6b3d1d5a5 (opens in a new tab)
- git.kernel.org/stable/c/24319f25b641e55f84e55455092a39a2485c78d4 (opens in a new tab)
- git.kernel.org/stable/c/bbd87eca5407288f2b63ff9357c611cd57e7e640 (opens in a new tab)