CVE-2026-90223

Linux · Kernel

The Linux kernel NFC LLCP implementation improperly validates SNL TLV length, allowing unauthenticated adjacent attackers to trigger out-of-bounds reads and potential denial of service conditions.

Executive summary

An unauthenticated attacker within physical proximity can exploit an out-of-bounds read vulnerability in the Linux kernel NFC stack to cause system instability or information leakage.

Vulnerability

This is an out-of-bounds read flaw in the nfc_llcp_recv_snl function, where insufficient validation of SNL TLV lengths allows an unauthenticated attacker to supply malformed data that causes memory access errors.

Business impact

Successful exploitation allows an adjacent attacker to crash the kernel, resulting in a denial of service for systems utilizing NFC features. While the CVSS score of 7.1 indicates a high severity, the requirement for physical proximity (adjacent network) limits the attack surface; however, impacted devices could be rendered unresponsive or forced into a reboot loop, causing significant operational downtime in environments relying on NFC connectivity.

Remediation

Immediate Action: Apply the latest kernel security updates provided by your distribution vendor, specifically ensuring versions 5.10.270, 5.15.221, 6.1.188, or 6.6.157 (or later) are deployed.

Proactive Monitoring: Monitor system logs for kernel panics or unexpected NFC driver restarts that may indicate attempted exploitation of the LLCP stack.

Compensating Controls: If patching is not immediately feasible, disable the NFC subsystem or blacklist the relevant kernel modules (such as nfc or llcp) on systems where NFC functionality is not strictly required.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the potential for system-wide instability, organizations should prioritize patching Linux-based systems that utilize NFC hardware. Administrators are advised to verify their kernel versions against the provided fixed releases and apply updates through their standard patch management lifecycle to mitigate this high-severity risk.

More Linux CVEs all →

History

CVE Brief tracked this CVE 4 days before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 7.1 (3.1) from cvelistV5
  4. Analyst report written

Sources