GHSA-8VVQ-JJHC-WFC4
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98482"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:16:58Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfc: llcp: drop truncated I/RR/RNR PDUs in nfc_llcp_recv_hdlc()\n\nnfc_llcp_recv_hdlc() reads the sequence byte skb-\u003edata[2], via\nnfc_llcp_ns()/nfc_llcp_nr(), before any length check. The receive path\nonly guarantees the two-byte LLCP header -- __nfc_llcp_recv() checks it\nwith pskb_may_pull() and nfc_llcp_recv_agf() admits two-byte inner PDUs\n-- so a two-byte I, RR or RNR PDU reads one byte of uninitialised skb\ntailroom. The byte becomes N(R)/N(S); a peer can already set those with\na well-formed PDU, so this is acting on uninitialised memory, not new\npeer control.\n\nGuard the read with pskb_may_pull(), as commit 95674f506c63 (\"nfc: llcp:\nreject PDUs shorter than the LLCP header\") did for the two-byte header,\nso the sequence byte is present and linear before it is read. RR and RNR\nPDUs are LLCP_HEADER_SIZE + LLCP_SEQUENCE_SIZE bytes and an I PDU is\nlonger, so no valid frame is rejected; a truncated PDU is malformed, so\nreturn without a DM reply.",
"id": "GHSA-8vvq-jjhc-wfc4",
"modified": "2026-10-18T18:31:50Z",
"published": "2026-10-18T18:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98482"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/066205553a0106565bcede934f5721c25ebd6e4e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/18f60ee882403d5b48097f5f6ae45f794e4cc643"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/273f9d667cde649f8de9d72b1303cc2f4b658c50"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3afdbebfee2ef7e9510880868cfb482cbffe6836"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/51b6d73373589abb9de4d84767b0db1bc8d395d9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/744e61bd06188d8bb068c26a461c252f242b05c9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/810f204ef8f61f0c930cf6b3280050b3ee6a8ae7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9b4086eb67a9a3b1ce69fef1b6793827363703ce"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.