CVE-2026-90223

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

HIGH
7.1
CVSS Score
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploit prediction
EPSS 0.4%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

19cfe5843e86cc95542d9d875c9386e197956d753.8
Vendor states this is fixed in 02030f95820c42431280f4f945ff34247fb840ff (fixed)
Vendor states this is fixed in 587fc2a5a35b41883b22b8f808fe5d345208914b (fixed)
Vendor states this is fixed in 749a9048bf51a668ec3ab6c0392ba32325607281 (fixed)
Vendor states this is fixed in 88b36d36e12c9ba76decdb580d9c1907c084e587 (fixed)
Vendor states this is fixed in 99fdb5c2522f365efa199d0117b641e35097041e (fixed)
Vendor states this is fixed in eeb16fb24cfe67947b832fd9ada5f488afc72579 (fixed)
Vendor states this is fixed in f04ac9bf2379f3e2470c400c235eb12f74891bef (fixed)
Vendor states this is fixed in f4c7f37f0ab990952539dc68d931d65c3657600a (fixed)
Vendor states this is fixed in 3.8 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card