CVE-2026-90223

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

Gravité et risque d'exploitation

CVE-2026-90223 obtient un score CVSS de 7.1/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.41 %, ce qui la place devant 34.2 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <88b36d36e12c9ba76decdb580d9c1907c084e587, <f04ac9bf2379f3e2470c400c235eb12f74891bef, 5.15.221, 5.10.270, 0, <eeb16fb24cfe67947b832fd9ada5f488afc72579, 6.1.188, 6.18.52, 19cfe5843e86cc95542d9d875c9386e197956d75, <f4c7f37f0ab990952539dc68d931d65c3657600a, <=5.10.*, <=6.6.*, 3.8, <587fc2a5a35b41883b22b8f808fe5d345208914b, <749a9048bf51a668ec3ab6c0392ba32325607281, 6.6.157, 7.2.6, <=6.18.*, <99fdb5c2522f365efa199d0117b641e35097041e, 6.12.110, <=7.2.*, <3.8, <=*, <=5.15.*, <02030f95820c42431280f4f945ff34247fb840ff, 7.3) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/88b36d36e12c9ba76decdb580d9c1907c084e587
• https://git.kernel.org/stable/c/587fc2a5a35b41883b22b8f808fe5d345208914b
• https://git.kernel.org/stable/c/f04ac9bf2379f3e2470c400c235eb12f74891bef
• https://git.kernel.org/stable/c/02030f95820c42431280f4f945ff34247fb840ff
• https://git.kernel.org/stable/c/99fdb5c2522f365efa199d0117b641e35097041e
• https://git.kernel.org/stable/c/749a9048bf51a668ec3ab6c0392ba32325607281
• https://git.kernel.org/stable/c/eeb16fb24cfe67947b832fd9ada5f488afc72579
• https://git.kernel.org/stable/c/f4c7f37f0ab990952539dc68d931d65c3657600a