CVE-2026-98482: Linux
EPSS: 0.2% probability of exploitation activity in the next 30 days.
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc() nfc_llcp_recv_hdlc() reads the sequence byte skb->data[2], via nfc_llcp_ns()/nfc_llcp_nr(), before any length check. The receive path only guarantees the two-byte LLCP header -- __nfc_llcp_recv() checks it with pskb_may_pull() and nfc_llcp_recv_agf() admits two-byte inner PDUs -- so a two-byte I, RR or RNR PDU reads one byte of uninitialised skb tailroom. The byte becomes N(R)/N(S); a peer can already set those with a well-formed PDU, so this is acting on uninitialised memory, not new peer control. Guard the read with pskb_may_pull(), as commit 95674f506c63 ("nfc: llcp: reject PDUs shorter than the LLCP header") did for the two-byte header, so the sequence byte is present and linear before it is read. RR and RNR PDUs are LLCP_HEADER_SIZE + LLCP_SEQUENCE_SIZE bytes and an I PDU is longer, so no valid frame is rejected; a truncated PDU is malformed, so return without a DM reply.
What to do
The record states a fixed version for each range of affected versions. Update to the one for the range your version is in: a later release on another branch may not have the fix.
- Linux, from 3.3, before 5.10.271: fixed in 5.10.271
- Linux, from 5.11, before 5.15.222: fixed in 5.15.222
- Linux, from 5.16, before 6.1.189: fixed in 6.1.189
- Linux, from 6.2, before 6.6.158: fixed in 6.6.158
- Linux, from 6.7, before 6.12.112: fixed in 6.12.112
- Linux, from 6.13, before 6.18.55: fixed in 6.18.55
- Linux, from 6.19, before 7.2.9: fixed in 7.2.9
Affected products
- Linux Linux: from 3.3, before 5.10.271 (fixed in 5.10.271); from 5.11, before 5.15.222 (fixed in 5.15.222); from 5.16, before 6.1.189 (fixed in 6.1.189); from 6.2, before 6.6.158 (fixed in 6.6.158); from 6.7, before 6.12.112 (fixed in 6.12.112); from 6.13, before 6.18.55 (fixed in 6.18.55); …
Published 2026-10-18. Last modified 2026-10-19.