In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: bound SNL TLV parsing to the skb and add length checks… (CVE-2026-90223)
A vulnerability in the Linux kernel's NFC LLCP implementation allowed out-of-bounds reads due to improper length checks when parsing SNL TLV data. This flaw could be triggered by a nearby NFC device without authentication, potentially causing denial of service. The issue was resolved by bounding TLV parsing to the actual skb data and adding explicit length validations.
AI Analysis
Technical Summary
The Linux kernel's nfc_llcp_recv_snl() function parsed SNL TLV lists using offsets and lengths derived from skb->len without properly bounding reads to the actual skb data. This led to three issues: underflow of tlv_len for short frames, reading TLV headers without verifying sufficient bytes remain, and out-of-bounds reads when declared TLV lengths exceeded buffer size. Specifically, SDREQ and SDRES TLVs lacked adequate length checks, causing size_t underflow and out-of-bounds memory access. The vulnerability could be exploited by a nearby NFC device without authentication since LLCP link activation is automatic after NFC-DEP. The fix involved walking the TLV list by pointer bounded by skb_tail_pointer(), validating each TLV's declared length, and adding explicit length checks for SDREQ and SDRES TLVs.
Potential Impact
An unauthenticated nearby attacker with NFC capability could trigger out-of-bounds reads in the kernel memory, potentially causing a denial of service (kernel crash). The CVSS score of 7.1 reflects a high severity with local network attack vector, low attack complexity, no privileges required, no user interaction, and partial confidentiality impact with high availability impact.
Mitigation Recommendations
A fix is available that bounds TLV parsing to the actual skb data and adds explicit length checks for TLV types. Users should apply the official Linux kernel patches that address this vulnerability. Since this is not a cloud service, remediation depends on updating affected Linux kernel versions. Patch status is not explicitly stated in the input data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: bound SNL TLV parsing to the skb and add length checks… (CVE-2026-90223)
Description
A vulnerability in the Linux kernel's NFC LLCP implementation allowed out-of-bounds reads due to improper length checks when parsing SNL TLV data. This flaw could be triggered by a nearby NFC device without authentication, potentially causing denial of service. The issue was resolved by bounding TLV parsing to the actual skb data and adding explicit length validations.
CVSS v3.1
Score 7.1high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's nfc_llcp_recv_snl() function parsed SNL TLV lists using offsets and lengths derived from skb->len without properly bounding reads to the actual skb data. This led to three issues: underflow of tlv_len for short frames, reading TLV headers without verifying sufficient bytes remain, and out-of-bounds reads when declared TLV lengths exceeded buffer size. Specifically, SDREQ and SDRES TLVs lacked adequate length checks, causing size_t underflow and out-of-bounds memory access. The vulnerability could be exploited by a nearby NFC device without authentication since LLCP link activation is automatic after NFC-DEP. The fix involved walking the TLV list by pointer bounded by skb_tail_pointer(), validating each TLV's declared length, and adding explicit length checks for SDREQ and SDRES TLVs.
Potential Impact
An unauthenticated nearby attacker with NFC capability could trigger out-of-bounds reads in the kernel memory, potentially causing a denial of service (kernel crash). The CVSS score of 7.1 reflects a high severity with local network attack vector, low attack complexity, no privileges required, no user interaction, and partial confidentiality impact with high availability impact.
Mitigation Recommendations
A fix is available that bounds TLV parsing to the actual skb data and adds explicit length checks for TLV types. Users should apply the official Linux kernel patches that address this vulnerability. Since this is not a cloud service, remediation depends on updating affected Linux kernel versions. Patch status is not explicitly stated in the input data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jxpm-782w-87ph
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-90223"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade52555bf5e2cf5edc1a3
Added to database: 09/19/2026, 01:28:05 UTC
Last enriched: 09/19/2026, 01:52:31 UTC
Last updated: 09/19/2026, 04:17:04 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.