CVE-2026-80798 — nfc: llcp: reject PDUs shorter than the LLCP header
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: reject PDUs shorter than the LLCP header Every LLCP PDU begins with a two-byte header (DSAP/SSAP + PTYPE), but the receive path never checked that a frame is at least LLCP_HEADER_SIZE bytes before parsing it. nfc_llcp_rx_skb() reads the header via nfc_llcp_ptype()/nfc_llcp_dsap()/ nfc_llcp_ssap(), which dereference pdu->data[0] and pdu->data[1], and a CONNECT or CC PDU then computes tlv_array_len = skb->len - LLCP_HEADER_SIZE; as a size_t and hands it to the TLV walk. When the frame is shorter than the header the subtraction wraps to a huge value and the walk runs far past the buffer, an out-of-bounds read. A nearby NFC device can reach this without authentication; LLCP link activation happens automatically after NFC-DEP. Guard the common receive choke point __nfc_llcp_recv(), shared by both the target (nfc_llcp_data_received()) and initiator (nfc_llcp_recv()) paths, so a short skb is dropped before the rx_work worker parses it. Use pskb_may_pull() rather than a skb->len test so the two header bytes are guaranteed to sit in the skb linear area even for a non-linear skb, matching how the sibling NCI and HCI receive paths validate their headers. Reproduced with a KFENCE out-of-bounds read via /dev/virtual_nci on linux-next. Found by 0sec automated security-research tooling (https://0sec.ai).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < e6ec76a68dce04884dfeccfe5a5f0e9f67c0ec82≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < f36cffea24bf3e2cc29a00d4b51dbcadc087d810≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < a7b9b449f5a5132221fff6adc11a9431ab8cd914≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < 3793d768b40f38bb97265dd5b9a8b8655c4e1b1d≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < eab47618e282602197db287ecbd1b09d356a2515≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < e969e98410051b1ef8cc318bfe0c7e3f24ec766d≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < ae5f20f5842f440b72d030e3a34fe182dd8eae42≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < d3d90243393c48146911c67fd3792b549d21d9e6 and 2 more≥ d646960f7986fefb460a2b062d5ccc8ccfeacc3a and < 95674f506c6376d6722a23144c9acd26609771edversion 3.3 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.29%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/95674f506c6376d6722a23144c9acd26609771ed
- git.kernel.org/stable/c/3793d768b40f38bb97265dd5b9a8b8655c4e1b1d
- github.com/advisories/GHSA-p65w-76hh-qj57
- git.kernel.org/stable/c/ae5f20f5842f440b72d030e3a34fe182dd8eae42
- git.kernel.org/stable/c/e6ec76a68dce04884dfeccfe5a5f0e9f67c0ec82
- git.kernel.org/stable/c/f36cffea24bf3e2cc29a00d4b51dbcadc087d810
- git.kernel.org/stable/c/d3d90243393c48146911c67fd3792b549d21d9e6
- git.kernel.org/stable/c/eab47618e282602197db287ecbd1b09d356a2515
- git.kernel.org/stable/c/a7b9b449f5a5132221fff6adc11a9431ab8cd914
- git.kernel.org/stable/c/e969e98410051b1ef8cc318bfe0c7e3f24ec766d
- nvd.nist.gov/vuln/detail/CVE-2026-80798
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 20h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 20h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 20h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 20h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 20h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 20h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80798 is "nfc: llcp: reject PDUs shorter than the LLCP header", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.