PatchSiren cyber security CVE debrief
CVE-2026-90223 Linux CVE debrief
A vulnerability in the Linux kernel's NFC LLCP implementation could allow an attacker to trigger an out-of-bounds read. The issue arises from improper parsing of SNL TLVs, which can lead to underflow and buffer overrun. A nearby NFC device can exploit this without authentication, as LLCP link activation occurs automatically after NFC-DEP. This vulnerability has a high severity score and requires immediate attention from Linux kernel developers and users with NFC capabilities. To mitigate this vulnerability, it is essential to review and apply the provided kernel patches to ensure the NFC LLCP implementation is properly bounded and validated.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-17
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-17
- Advisory updated
- 2026-09-18
Who should care
Linux kernel developers and maintainers, as well as users of Linux-based systems with NFC capabilities, should assess their exposure to this vulnerability and apply patches or mitigations as necessary.
Why it matters
CVE-2026-90223 is a high-severity vulnerability in the Linux kernel's NFC LLCP implementation that could allow an attacker to trigger an out-of-bounds read, potentially leading to system crashes or information disclosure. Linux kernel developers and users with NFC capabilities should assess their exposure and apply patches or mitigations.
- Verify NFC LLCP implementation bounds and validation to prevent out-of-bounds reads.
- Assess exposure of Linux kernel implementations with NFC capabilities.
- Monitor for unusual NFC activity and implement additional logging and monitoring.
Technical summary
The Linux kernel's NFC LLCP implementation has a vulnerability that allows an attacker to trigger an out-of-bounds read. This occurs due to improper parsing of SNL TLVs, which can lead to underflow and buffer overrun. The vulnerability can be exploited by a nearby NFC device without authentication, as LLCP link activation happens automatically after NFC-DEP. The vulnerability was found by 0sec automated security-research tooling, and its exploitation could potentially lead to system crashes or information disclosure. To prevent exploitation, it is crucial to review and apply the provided kernel patches and verify that NFC-DEP is properly configured and secured.
Defensive priority
High
Recommended defensive actions
- Review and apply the provided kernel patches to ensure the NFC LLCP implementation is properly bounded and validated.
- Verify that NFC-DEP is properly configured and secured in your Linux kernel implementation.
- Monitor for any unusual NFC activity and implement additional logging and monitoring to detect potential exploitation attempts.
- Perform a thorough review of the Linux kernel implementation to identify any potential vulnerabilities.
- Conduct regular security audits to ensure the Linux kernel is up-to-date and secure.
- Implement compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The vulnerability was found by 0sec automated security-research tooling. The CVE record and NVD entry provide details on the issue, but the scope of affected systems and versions is not explicitly stated.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90223 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90223
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90223 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90223
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/02030f95820c42431280f4f945ff34247fb840ff
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/587fc2a5a35b41883b22b8f808fe5d345208914b
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/749a9048bf51a668ec3ab6c0392ba32325607281
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/88b36d36e12c9ba76decdb580d9c1907c084e587
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/99fdb5c2522f365efa199d0117b641e35097041e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/eeb16fb24cfe67947b832fd9ada5f488afc72579
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f04ac9bf2379f3e2470c400c235eb12f74891bef
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f4c7f37f0ab990952539dc68d931d65c3657600a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.