CVE-2026-90223: Linux Vulnerability (CVSS 7.1)

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

Metrics

CVSS 3.1

7.1/10

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 19cfe5843e86cc95542d9d875c9386e197956d75, < 88b36d36e12c9ba76decdb580d9c1907c084e587; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < 587fc2a5a35b41883b22b8f808fe5d345208914b; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < f04ac9bf2379f3e2470c400c235eb12f74891bef; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < 02030f95820c42431280f4f945ff34247fb840ff; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < 99fdb5c2522f365efa199d0117b641e35097041e; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < 749a9048bf51a668ec3ab6c0392ba32325607281; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < eeb16fb24cfe67947b832fd9ada5f488afc72579; >= 19cfe5843e86cc95542d9d875c9386e197956d75, < f4c7f37f0ab990952539dc68d931d65c3657600a
Linux	Linux	3.8

References

Timeline

Published: Sep 17, 2026
Last Modified: Sep 18, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-90223?

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

How severe is CVE-2026-90223?

CVE-2026-90223 has a CVSS score of 7.1/10 (HIGH severity).

How do I fix CVE-2026-90223?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →