CVE-2026-98481: Linux kernel · nfc: port100: reject frames whose declared length exceeds the received data
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e4da1452e10c6472a4bac48dc2f6a35fff1fcd69 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 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 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e4da1452e10c6472a4bac48dc2f6a35fff1fcd69, db66a30588630c7de30ef033f00daddef69f6ad9, 035056e07ea65be670284246d9bc62f2f00ff4a3 +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
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits. Users should update their Linux kernel to a version that includes the fix identified by the provided commit hashes. No additional mitigation is required once the kernel is updated.
Description
A vulnerability in the Linux kernel NFC port100 driver allows out-of-bounds memory read due to improper validation of frame length fields. The driver fails to verify that the declared frame length does not exceed the actual received data length, leading to potential buffer over-read. This issue has been fixed by rejecting frames whose declared length exceeds the received data before validation.
References
- git.kernel.org/stable/c/0d482995f0cdd0302450aa300c684c642d8ab31f (opens in a new tab)
- git.kernel.org/stable/c/9e8df087826b9999d1b83b06f5d85675d5a69c9e (opens in a new tab)
- git.kernel.org/stable/c/db66a30588630c7de30ef033f00daddef69f6ad9 (opens in a new tab)
- git.kernel.org/stable/c/144ad477c381e2c592b64898d04ab4ce03b32861 (opens in a new tab)
- git.kernel.org/stable/c/e4da1452e10c6472a4bac48dc2f6a35fff1fcd69 (opens in a new tab)
- git.kernel.org/stable/c/14b1467cfc6630583650f33538174c5a1ec685ab (opens in a new tab)
- git.kernel.org/stable/c/035056e07ea65be670284246d9bc62f2f00ff4a3 (opens in a new tab)
- git.kernel.org/stable/c/092c6a605cbd6414ef499834c2e0da69c2c3388e (opens in a new tab)