CVE-2026-80800 json
nfc: llcp: bound the connect_sn TLV walk to the skb
published 2026-09-04 2 mo ago modified 2026-10-19 21 d ago also EUVD-2026-71235
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
nfc: llcp: bound the connect_sn TLV walk to the skb
Commit 27256cdb290e ("nfc: llcp: bound SNL TLV parsing to the skb and add length checks") fixed the unbounded TLV walk in nfc_llcp_recv_snl(), and commit d8bd2dedbde5 ("nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers") subsequently bounded nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv(). One sibling parser sharing the same pattern remains unbounded: nfc_llcp_connect_sn().
nfc_llcp_connect_sn() walks a TLV list, reading a two-byte header (type, length) followed by length bytes of value, without checking that the two header bytes or the declared length stay within the buffer. It returns a pointer to a service name of up to 255 bytes that may point past the end of the skb; it is subsequently consumed by memcmp() in nfc_llcp_sock_from_sn(). In addition tlv_array_len was computed as "skb->len - LLCP_HEADER_SIZE" in size_t, so a CONNECT/CC frame shorter than the LLCP header underflows to a huge length and the walk runs far past the buffer.
nfc_llcp_connect_sn() is reachable from nfc_llcp_recv_connect() and nfc_llcp_recv_cc(), i.e. from received CONNECT and CC PDUs. A nearby NFC device can reach this without authentication; LLCP link activation happens automatically after NFC-DEP, and the nfc_llcp_rx_skb() dispatcher applies no minimum-length guard.
Walk the TLV list by pointer, bounded by skb_tail_pointer(skb), and validate each declared length before use, matching the approach already used for nfc_llcp_recv_snl(). Starting the walk at &skb->data[LLCP_HEADER_SIZE] against the tail pointer also removes the size_t underflow for short frames.
Found by 0sec automated security-research tooling (https://0sec.ai).
Patch / fix
- Linux Linux 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, 7.2.1, 7.3
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.107-1
- linux Debian 14 7.1.12-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-80800
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-80800
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default Linux Micro 6.0 6.4.0-159998.55.1
- kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
- kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.90.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.90.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.90.1
suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:5091-1SUSE-SU-2026:4687-1
- kernel-source openSUSE Tumbleweed 7.2.5-1.1
opensuse advisories openSUSE-SU-2026:11773-1
- git.kernel.org/stable/c/b2ebdfe3d5b76e91f267a61cbc3f9a0e3f77071e commit
- git.kernel.org/stable/c/e18d044bab6d3d0280639098c3fe6621692cbfe2 commit
- git.kernel.org/stable/c/65a0ec7783b06068dda6745dd689bf4a91ee64aa commit
- git.kernel.org/stable/c/1964addc8dd535a05d5d3b55b4d1ac19ae31aa65 commit
- git.kernel.org/stable/c/389986fd79e4d43f971a03b512645a1bb63c982f commit
- git.kernel.org/stable/c/e87527b506c40db9af528714b7b1240918eb80fc commit
- git.kernel.org/stable/c/22e5177ba1196a0b272a6a46c2575eb940a939c4 commit
- git.kernel.org/stable/c/0cfbdb0e13ab5b0765d77f96af67eb879cbc9736 commit
- git.kernel.org/stable/c/55c68ac93e7dacc0f5f608b9c39dd4ff48cf28e8 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80800 updated cvss 5.5
kernel: nfc: llcp: bound the connect_sn TLV walk to the skb
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b2ebdfe3d5b76e91f267a61cbc3f9a0e3f77071e
- git.kernel.org /stable/c/e18d044bab6d3d0280639098c3fe6621692cbfe2
- git.kernel.org /stable/c/65a0ec7783b06068dda6745dd689bf4a91ee64aa
- git.kernel.org /stable/c/1964addc8dd535a05d5d3b55b4d1ac19ae31aa65
- git.kernel.org /stable/c/389986fd79e4d43f971a03b512645a1bb63c982f
- git.kernel.org /stable/c/e87527b506c40db9af528714b7b1240918eb80fc
- git.kernel.org /stable/c/22e5177ba1196a0b272a6a46c2575eb940a939c4
- git.kernel.org /stable/c/0cfbdb0e13ab5b0765d77f96af67eb879cbc9736
- git.kernel.org /stable/c/55c68ac93e7dacc0f5f608b9c39dd4ff48cf28e8
Sources
- CVE List CVE-2026-80800
- NVD CVE-2026-80800
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.