PatchSiren cyber security CVE debrief
CVE-2026-80800 Linux CVE debrief
A vulnerability in the Linux kernel's NFC LLCP implementation allows for an unbounded TLV walk in the nfc_llcp_connect_sn() function. This can be triggered by a nearby NFC device without authentication, as LLCP link activation occurs automatically after NFC-DEP. The issue has been resolved by bounding the TLV list walk by the skb and validating each declared length before use.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-04
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-09-04
- Advisory updated
- 2026-10-19
Who should care
Defenders responsible for Linux kernel and NFC implementation security should assess exposure and prioritize patching. This includes operators, security teams, and vulnerability management teams that need to verify patch application, review NFC implementation for potential exposure, and monitor for potential exploitation attempts.
Why it matters
CVE-2026-80800 is a vulnerability in the Linux kernel's NFC LLCP implementation that allows for an unbounded TLV walk. Defenders should prioritize verifying and applying patches, reviewing NFC implementation for potential exposure, and monitoring for potential exploitation attempts.
- Potential for out-of-bounds reads and denial of service
- Requires verification of patch application and NFC implementation security
- May allow for exploitation by nearby NFC devices without authentication
Technical summary
The nfc_llcp_connect_sn() function in the Linux kernel's NFC LLCP implementation did not properly bound the TLV list walk, allowing for potential out-of-bounds reads. This has been resolved through patches that bound the walk and validate lengths. The issue allows for an unbounded TLV walk in the nfc_llcp_connect_sn() function, which can be triggered by a nearby NFC device without authentication, as LLCP link activation occurs automatically after NFC-DEP. The commits that fixed the issue are 27256cdb290e and d8bd2dedbde5.
Defensive priority
Defenders should prioritize verifying and applying patches for this vulnerability, particularly for systems using NFC functionality.
Recommended defensive actions
- Verify and apply patches for this vulnerability
- Review NFC implementation for potential exposure
- Monitor for potential exploitation attempts
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
Evidence notes
The vulnerability was found by 0sec automated security-research tooling and resolved through commits that bound the TLV walk and validated lengths. The issue is reachable from nfc_llcp_recv_connect() and nfc_llcp_recv_cc(), i.e., from received CONNECT and CC PDUs. A nearby NFC device can reach this without authentication; LLCP link activation happens automatically after NFC-DEP. Defenders should verify patch application, review NFC implementation for potential exposure, and monitor for potential exploitation attempts. The commits that
Sources and references
Verified primary and authoritative sources
-
CVE-2026-80800 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-80800
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-80800 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80800
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/0cfbdb0e13ab5b0765d77f96af67eb879cbc9736
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1964addc8dd535a05d5d3b55b4d1ac19ae31aa65
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/22e5177ba1196a0b272a6a46c2575eb940a939c4
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/389986fd79e4d43f971a03b512645a1bb63c982f
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/55c68ac93e7dacc0f5f608b9c39dd4ff48cf28e8
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/65a0ec7783b06068dda6745dd689bf4a91ee64aa
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/b2ebdfe3d5b76e91f267a61cbc3f9a0e3f77071e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e18d044bab6d3d0280639098c3fe6621692cbfe2
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.