CVE-2026-98931: Linux kernel · mtd: spinand: fix NULL pointer dereference with no ECC engine
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fc2f651f520394893b14b75281a01e502bfa73bb : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fc2f651f520394893b14b75281a01e502bfa73bb, b890e6163761ddb580cc74f43e15f8bbde15647e, 80e8b0ea73ba295e92dfb6cf1c41df9da64234c6 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: mtd: spinand: fix NULL pointer dereference with no ECC engine When "nand-no-ecc-engine" is set in DT, nanddev_get_ecc_engine() takes the NAND_ECC_ENGINE_TYPE_NONE path and returns success while leaving nand->ecc.engine NULL. The SPI-NAND code nevertheless dereferences it unconditionally to test for a pipelined engine, so probing such a device oopses immediately. Rather than open-coding the test three times, add a nand_ecc_is_pipelined() helper to the NAND core that folds the NULL check into the integration comparison, and use it everywhere. Future callers then cannot reintroduce the problem.
References
- git.kernel.org/stable/c/77c449c9c946fc420008dc55cd30f53749c915e4 (opens in a new tab)
- git.kernel.org/stable/c/3c765fd5212c1bbc71568b1518a7ec963a7040b4 (opens in a new tab)
- git.kernel.org/stable/c/80e8b0ea73ba295e92dfb6cf1c41df9da64234c6 (opens in a new tab)
- git.kernel.org/stable/c/fc2f651f520394893b14b75281a01e502bfa73bb (opens in a new tab)
- git.kernel.org/stable/c/b890e6163761ddb580cc74f43e15f8bbde15647e (opens in a new tab)