VDB

CVE-2026-80800

CVE-2026-80800 PUBLISHED

nfc: llcp: bound the connect_sn TLV walk to the skb

Reported by linux · Published September 4, 2026

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

EPSS 0.23% · 14.4th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinuxe87527b506c40db9af528714b7b1240918eb80fc, e18d044bab6d3d0280639098c3fe6621692cbfe2, b2ebdfe3d5b76e91f267a61cbc3f9a0e3f77071e, 65a0ec7783b06068dda6745dd689bf4a91ee64aa, 55c68ac93e7dacc0f5f608b9c39dd4ff48cf28e8, 389986fd79e4d43f971a03b512645a1bb63c982f, 22e5177ba1196a0b272a6a46c2575eb940a939c4, 1964addc8dd535a05d5d3b55b4d1ac19ae31aa65, 0cfbdb0e13ab5b0765d77f96af67eb879cbc9736

Risk scores

EPSS Score
0.23%
14.4th percentile

Affected products

VendorProductVersions
LinuxLinuxd646960f7986fefb460a2b062d5ccc8ccfeacc3a, d646960f7986fefb460a2b062d5ccc8ccfeacc3a, d646960f7986fefb460a2b062d5ccc8ccfeacc3a
LinuxLinux3.3, 0, 5.10.267
LinuxLinux7.3, 0, 5.10.267
linuxlinux_kernel3.3, 3.3, 3.3

Timeline

  • Sep 4, 2026 Coalition ESS Score
  • Sep 4, 2026 CVE Published
  • Sep 5, 2026 EPSS Score (20 in total, the first dated here)
  • Oct 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-80800
vulnetix vdb fixes CVE-2026-80800

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80800/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›