---
title: "CVE-2026-90223: Linux kernel NFC llcp - Out-of-Bounds Read"
description: "Linux kernel NFC llcp contains an out-of-bounds read vulnerability caused by unbounded SNL TLV parsing in nfc_llcp_recv_snl(), letting nearby attackers cause memory corruption or denial of service, exploit requires NFC link activation."
url: https://panop.io/threat-heartbeat/CVE-2026-90223/
---

# CVE-2026-90223 Linux kernel NFC llcp - Out-of-Bounds Read

Linux kernel NFC llcp contains an out-of-bounds read vulnerability caused by unbounded SNL TLV parsing in nfc\_llcp\_recv\_snl(), letting nearby attackers cause memory corruption or denial of service, exploit requires NFC link activation.

CVSS base score 7.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.47% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-90223)

## Details

Type

Out-of-Bounds Read

Impact

Denial Of Service

CVSS vector

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

Published

17 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version with the fix for bounded SNL TLV parsing and length checks.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-90223](https://nvd.nist.gov/vuln/detail/CVE-2026-90223)
- [https://git.kernel.org/stable/c/f4c7f37f0ab990952539dc68d931d65c3657600a](https://git.kernel.org/stable/c/f4c7f37f0ab990952539dc68d931d65c3657600a)
- [https://git.kernel.org/stable/c/02030f95820c42431280f4f945ff34247fb840ff](https://git.kernel.org/stable/c/02030f95820c42431280f4f945ff34247fb840ff)
- [https://git.kernel.org/stable/c/587fc2a5a35b41883b22b8f808fe5d345208914b](https://git.kernel.org/stable/c/587fc2a5a35b41883b22b8f808fe5d345208914b)
- [https://git.kernel.org/stable/c/749a9048bf51a668ec3ab6c0392ba32325607281](https://git.kernel.org/stable/c/749a9048bf51a668ec3ab6c0392ba32325607281)
- [https://git.kernel.org/stable/c/88b36d36e12c9ba76decdb580d9c1907c084e587](https://git.kernel.org/stable/c/88b36d36e12c9ba76decdb580d9c1907c084e587)
- [https://git.kernel.org/stable/c/99fdb5c2522f365efa199d0117b641e35097041e](https://git.kernel.org/stable/c/99fdb5c2522f365efa199d0117b641e35097041e)
- [https://git.kernel.org/stable/c/eeb16fb24cfe67947b832fd9ada5f488afc72579](https://git.kernel.org/stable/c/eeb16fb24cfe67947b832fd9ada5f488afc72579)
- [https://git.kernel.org/stable/c/f04ac9bf2379f3e2470c400c235eb12f74891bef](https://git.kernel.org/stable/c/f04ac9bf2379f3e2470c400c235eb12f74891bef)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
