CVE-2026-98578: Linux kernel · nfc: st21nfca: validate ISO15693 inventory length
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fdd95e819d828c975aaeb258a3fed5dd7fd136d0 : 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 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fdd95e819d828c975aaeb258a3fed5dd7fd136d0, e47b2a350bb0ff123434ec5484c6dc3333b0727c, a86987d03a4d39acdbe4533d83db4d656ea36c59 +5
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
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix has been implemented in the Linux kernel source code, as indicated by the presence of multiple fixed commit versions. Users and administrators should update to a Linux kernel version that includes these fixes to remediate the vulnerability.
Description
A vulnerability in the Linux kernel's NFC subsystem (st21nfca driver) related to ISO15693 inventory length validation has been resolved. The issue involved improper validation of a two-byte prefix and subsequent data length checks, which could lead to incorrect processing of NFC data. The fix enforces the presence of the prefix and requires at least two remaining bytes before copying UID data and reading the DSFID.
References
- git.kernel.org/stable/c/e47b2a350bb0ff123434ec5484c6dc3333b0727c (opens in a new tab)
- git.kernel.org/stable/c/57d183764f3002f9625ee4deeeb20716c519534e (opens in a new tab)
- git.kernel.org/stable/c/3af2ea4035581a1607d9830779c187a0c7e225aa (opens in a new tab)
- git.kernel.org/stable/c/9fa21b0f78adb514e3bd96a505ddb752e9727ff3 (opens in a new tab)
- git.kernel.org/stable/c/6353dae51bc9b3cad13c9d890b53311a46c96b4e (opens in a new tab)
- git.kernel.org/stable/c/fdd95e819d828c975aaeb258a3fed5dd7fd136d0 (opens in a new tab)
- git.kernel.org/stable/c/a86987d03a4d39acdbe4533d83db4d656ea36c59 (opens in a new tab)
- git.kernel.org/stable/c/7f2ea5ed588c03d481f0301e6c3d4240132383fb (opens in a new tab)