VulnerabilityPublished 18 Oct 2026

CVE-2026-98482: Linux kernel · nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc()

Source GCVE Database

Authoritative record:CVE-2026-98482· Medium

Not known to be exploited · fixed in 066205553a0106565bcede934f5721c25ebd6e4e : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

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 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-8vvq-jjhc-wfc4

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 066205553a0106565bcede934f5721c25ebd6e4e	Fixed in 066205553a0106565bcede934f5721c25ebd6e4e
LinuxLinux	Affected ≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 810f204ef8f61f0c930cf6b3280050b3ee6a8ae7	Fixed in 810f204ef8f61f0c930cf6b3280050b3ee6a8ae7
LinuxLinux	Affected ≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 744e61bd06188d8bb068c26a461c252f242b05c9	Fixed in 744e61bd06188d8bb068c26a461c252f242b05c9
LinuxLinux	Affected ≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 273f9d667cde649f8de9d72b1303cc2f4b658c50	Fixed in 273f9d667cde649f8de9d72b1303cc2f4b658c50
LinuxLinux	Affected ≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 51b6d73373589abb9de4d84767b0db1bc8d395d9	Fixed in 51b6d73373589abb9de4d84767b0db1bc8d395d9
LinuxLinux	Affected ≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a, < 18f60ee882403d5b48097f5f6ae45f794e4cc643	Fixed in 18f60ee882403d5b48097f5f6ae45f794e4cc643

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 applied in the Linux kernel to add proper length checks before reading the sequence byte in nfc_llcp_recv_hdlc(). Users should update to the fixed kernel version containing commit 95674f506c63 or later. No additional mitigation is required as the vulnerability is addressed by this official fix.

Description

A vulnerability in the Linux kernel NFC subsystem's LLCP receive handler was resolved. The function nfc_llcp_recv_hdlc() reads a sequence byte from a packet without verifying the packet length first, potentially accessing uninitialized memory. This occurs because the receive path only guarantees a two-byte LLCP header, but the sequence byte read happens before confirming the packet is long enough. The fix adds a length check to ensure the sequence byte is only read if present, dropping truncated PDUs without processing them.

References

Community reviews

Loading reviews…