# CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers CVE-2026-80799 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2026-80799, released September 5, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-80799 - Priority: High - CVSS: 8.1 (Important) - EPSS: 0.0023 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Sep 4, 2026 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-80799 ## Description In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain three related bugs in their TLV parsing loops: 1. 'offset' is declared u8 but tlv_array_len is u16. When TLV data advances offset past 255 it silently wraps to zero, causing infinite loops or double-processing of buffer data. 2. Before reading tlv[0] (type) and tlv[1] (length) there is no check that offset+2 <= tlv_array_len. A truncated TLV causes an OOB read of one byte past the buffer end. 3. After reading the length field, the value bytes are accessed without checking offset+2+length <= tlv_array_len. A crafted length=0xFF on a short buffer causes up to 255 bytes of OOB read past the buffer end. Both functions are reachable without authentication via nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes directly into nfc_llcp_parse_gb_tlv() with no additional validation. Fix all three issues by widening offset from u8 to u16 and adding bounds checks for both the TLV header and value field before each access. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 15.6 | 6.4.0-150600.23.138.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 15.6 | 6.4.0-150600.23.138.1.150600.12.64.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.84.1.150700.17.47.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 15.6 | 6.4.0-150600.23.138.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP6_Update_32 sles 15.6 | 1-150600.13.3.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7-RT_Update_21 sles 15.7 | 1-150700.1.3.1 | [SUSE-SU-2026:4640-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4640-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7_Update_22 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build sles 15.6 | 6.4.0-150600.23.138.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 15.6 | 6.4.0-150600.23.138.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 15.6 | 6.4.0-150600.23.138.1 | [SUSE-SU-2026:4660-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4660-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | linux Debian 12.15 (bookworm) | 6.1.187-1 | [DEBIAN-CVE-2026-80799](https://patchblox.com/security/data/fix/linux/debian-cve-2026-80799.md) | Sep 5, 2026 | | Linux | linux Debian 13.5 (trixie) | 6.12.107-1 | [DEBIAN-CVE-2026-80799](https://patchblox.com/security/data/fix/linux/debian-cve-2026-80799.md) | Sep 5, 2026 | | Linux | linux Debian 14 | 7.1.12-1 | [DEBIAN-CVE-2026-80799](https://patchblox.com/security/data/fix/linux/debian-cve-2026-80799.md) | Sep 5, 2026 | | Linux | linux-6.12 Debian 12.15 (bookworm) | 6.12.107-1~deb12u1 | [DEBIAN-CVE-2026-80799](https://patchblox.com/security/data/fix/linux/debian-cve-2026-80799.md) | Sep 5, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.