CVE-2026-90223

CVE CVE-2026-90223EUVD EUVD-2026-81816Published 2026-09-17T16:07:33.000ZLast changed 2026-09-18T17:53:49.000ZCVSS 7.1

What the advisory describes

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

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 19cfe5843e86cc95542d9d875c9386e197956d75 <f04ac9bf2379f3e2470c400c235eb12f74891bef; patch: 7.2.6; patch: 6.18.52; 19cfe5843e86cc95542d9d875c9386e197956d75 <587fc2a5a35b41883b22b8f808fe5d345208914b; patch: 0; 19cfe5843e86cc95542d9d875c9386e197956d75 <99fdb5c2522f365efa199d0117b641e35097041e; 3.8; 19cfe5843e86cc95542d9d875c9386e197956d75 <88b36d36e12c9ba76decdb580d9c1907c084e587; 19cfe5843e86cc95542d9d875c9386e197956d75 <02030f95820c42431280f4f945ff34247fb840ff; patch: 5.10.270; patch: 6.12.110; 19cfe5843e86cc95542d9d875c9386e197956d75 <eeb16fb24cfe67947b832fd9ada5f488afc72579; patch: 6.1.188; patch: 6.6.157; patch: 7.3-rc1; patch: 5.15.221; 19cfe5843e86cc95542d9d875c9386e197956d75 <f4c7f37f0ab990952539dc68d931d65c3657600a; 19cfe5843e86cc95542d9d875c9386e197956d75 <749a9048bf51a668ec3ab6c0392ba32325607281

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.