CVE-2026-98482: Linux kernel · nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 066205553a0106565bcede934f5721c25ebd6e4e : 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 066205553a0106565bcede934f5721c25ebd6e4e, 810f204ef8f61f0c930cf6b3280050b3ee6a8ae7, 744e61bd06188d8bb068c26a461c252f242b05c9 +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 is available and has been applied in the Linux kernel. The patch adds proper length checks before reading the sequence byte in nfc_llcp_recv_hdlc(), rejecting truncated PDUs. Users should update their Linux kernel to a version containing the fix commits referenced in the established facts to mitigate this issue.
Description
A vulnerability in the Linux kernel's NFC LLCP implementation allows reading uninitialized memory when processing truncated I, RR, or RNR PDUs. This occurs because the sequence byte is read before verifying the PDU length, potentially leading to use of uninitialized data. The issue is fixed by adding proper length checks to ensure the sequence byte is only read when present.
References
- git.kernel.org/stable/c/3afdbebfee2ef7e9510880868cfb482cbffe6836 (opens in a new tab)
- git.kernel.org/stable/c/9b4086eb67a9a3b1ce69fef1b6793827363703ce (opens in a new tab)
- git.kernel.org/stable/c/51b6d73373589abb9de4d84767b0db1bc8d395d9 (opens in a new tab)
- git.kernel.org/stable/c/066205553a0106565bcede934f5721c25ebd6e4e (opens in a new tab)
- git.kernel.org/stable/c/18f60ee882403d5b48097f5f6ae45f794e4cc643 (opens in a new tab)
- git.kernel.org/stable/c/810f204ef8f61f0c930cf6b3280050b3ee6a8ae7 (opens in a new tab)
- git.kernel.org/stable/c/744e61bd06188d8bb068c26a461c252f242b05c9 (opens in a new tab)
- git.kernel.org/stable/c/273f9d667cde649f8de9d72b1303cc2f4b658c50 (opens in a new tab)