CVE-2026-80799

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers

nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain three related bugs in their TLV parsing loops:

  • 'offset' is declared u8 but tlv_array_len is u16. When TLV data
advances offset past 255 it silently wraps to zero, causing infinite loops or double-processing of buffer data.
  • Before reading tlv[0] (type) and tlv[1] (length) there is no
check that offset+2 <= tlv_array_len. A truncated TLV causes an OOB read of one byte past the buffer end.
  • After reading the length field, the value bytes are accessed
without checking offset+2+length <= tlv_array_len. A crafted length=0xFF on a short buffer causes up to 255 bytes of OOB read past the buffer end.

Both functions are reachable without authentication via nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes directly into nfc_llcp_parse_gb_tlv() with no additional validation.

Fix all three issues by widening offset from u8 to u16 and adding bounds checks for both the TLV header and value field before each access.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 4, 2026

References (9)

Vendor Advisories for CVE-2026-80799(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)6.1.187-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (34 versions)6.12.107-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (169 versions)7.1.12-1—

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 09:03 UTCGHSA enrichment
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 15:20 UTCGHSA enrichment
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-12 21:37 UTCGHSA enrichment
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-10 03:54 UTCGHSA enrichment
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-07 10:09 UTCEG score recompute
  14. 2026-09-07 10:09 UTCGHSA enrichment
  15. 2026-09-06 13:48 UTCEPSS rescore
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-04 16:22 UTCNVD update
  18. 2026-09-04 15:29 UTCEG score recompute
  19. 2026-09-04 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80799?
CVE-2026-80799 is a publicly disclosed vulnerability published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers nfcllcpparsegbtlv() and nfcllcpparseconnectiontlv() contain three related bugs in their TLV parsing loops: 1. 'offset' is declared u8 but tlvarraylen is u16. When TLV data…
When was CVE-2026-80799 disclosed?
CVE-2026-80799 was first published in the National Vulnerability Database on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80799 actively exploited?
CVE-2026-80799 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.4% of all scored CVEs.
How do I remediate CVE-2026-80799?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80799, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80799

Explore →

Is Your Infrastructure Affected by CVE-2026-80799?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs