CVE-2026-90223

published 17 Sep 2026 · updated 20 Nov 2026

nfc: llcp: bound SNL TLV parsing to the skb and add length checks

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f4c7f37f0ab990952539dc68d931d65c3657600a, Kernel 02030f95820c42431280f4f945ff34247fb840ff, Kernel 587fc2a5a35b41883b22b8f808fe5d345208914b and 12 more.

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: bound SNL TLV parsing to the skb and add length checks nfc_llcp_recv_snl() walked the SNL TLV list using a u16 offset/length pair derived from skb->len, without bounding reads to the actual skb data. Three problems followed: - For a short frame (skb->len < LLCP_HEADER_SIZE), tlv_len underflowed. - The per-TLV header (type, length) was read without checking that two bytes remained. - A declared TLV length could run past the end of the buffer, and an SDREQ with length == 0 made "service_name_len = length - 1" underflow (size_t), driving an out-of-bounds read in the following strncmp() / nfc_llcp_sock_from_sn(). The SDRES case likewise read tlv[2]/tlv[3] without a length check. A nearby NFC device can reach this without authentication; LLCP link activation happens automatically after NFC-DEP. Walk the TLV list by pointer, bounded by skb_tail_pointer() over the linear skb data, and validate each TLV declared length before use. Add explicit length checks for SDREQ (>= 1) and SDRES (exactly 2). Found by 0sec automated security-research tooling (https://0sec.ai).

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=19cfe5843e86cc95542d9d875c9386e197956d75 <f4c7f37f0ab990952539dc68d931d65c3657600a, >=19cfe5843e86cc95542d9d875c9386e197956d75 <02030f95820c42431280f4f945ff34247fb840ff, >=19cfe5843e86cc95542d9d875c9386e197956d75 <587fc2a5a35b41883b22b8f808fe5d345208914b, >=19cfe5843e86cc95542d9d875c9386e197956d75 <749a9048bf51a668ec3ab6c0392ba32325607281, >=19cfe5843e86cc95542d9d875c9386e197956d75 <88b36d36e12c9ba76decdb580d9c1907c084e587, >=19cfe5843e86cc95542d9d875c9386e197956d75 <99fdb5c2522f365efa199d0117b641e35097041e, >=19cfe5843e86cc95542d9d875c9386e197956d75 <eeb16fb24cfe67947b832fd9ada5f488afc72579, >=19cfe5843e86cc95542d9d875c9386e197956d75 <f04ac9bf2379f3e2470c400c235eb12f74891bef, =3.8f4c7f37f0ab990952539dc68d931d65c3657600a, 02030f95820c42431280f4f945ff34247fb840ff, 587fc2a5a35b41883b22b8f808fe5d345208914b, 749a9048bf51a668ec3ab6c0392ba32325607281, 88b36d36e12c9ba76decdb580d9c1907c084e587, 99fdb5c2522f365efa199d0117b641e35097041e, eeb16fb24cfe67947b832fd9ada5f488afc72579, f04ac9bf2379f3e2470c400c235eb12f74891bef
linux-kernel: Kernel>=5.11.0 <5.15.221, >=5.16.0 <6.1.188, >=6.13.0 <6.18.52, >=6.19.0 <7.2.6, >=6.2.0 <6.6.157, >=6.7.0 <6.12.110, >=3.8.0 <5.10.2705.15.221, 6.1.188, 6.18.52, 7.2.6, 6.6.157, 6.12.110, 5.10.270

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90223 severity on Zeptric[![CVE-2026-90223](https://zeptric.io/badge/cve/CVE-2026-90223.svg)](https://zeptric.io/cve/CVE-2026-90223)