CVE-2026-80803

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
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: digital: clamp SENSF_RES length to the destination buffer

digital_in_recv_sensf_res() memcpy()s resp->len bytes from a remote NFC-F device response into the NFC_SENSF_RES_MAXSIZE-byte target.sensf_res field without an upper-bound check. A nearby malicious NFC-F device can send an oversized SENSF_RES response to overflow the stack-local struct nfc_target.

Clamp resp->len to NFC_SENSF_RES_MAXSIZE before the copy.

Found by 0sec automated security-research tooling (https://0sec.ai).

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
10%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 4, 2026

References (9)

Vendor Advisories for CVE-2026-80803(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 9× in last 7d / 21× 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-16 18:28 UTCVendor advisory
  3. 2026-09-16 18:28 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-13 16:24 UTCVendor advisory
  9. 2026-09-13 16:24 UTCGHSA enrichment
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-10 16:27 UTCGHSA enrichment
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-07 16:23 UTCEG score recompute
  15. 2026-09-07 16:23 UTCVendor advisory
  16. 2026-09-07 16:23 UTCGHSA enrichment
  17. 2026-09-06 13:48 UTCEPSS rescore
  18. 2026-09-05 15:31 UTCEPSS rescore
  19. 2026-09-04 16:22 UTCNVD update
  20. 2026-09-04 15:29 UTCEG score recompute
  21. 2026-09-04 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80803?
CVE-2026-80803 is a publicly disclosed vulnerability published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: nfc: digital: clamp SENSF_RES length to the destination buffer digitalinrecvsensfres() memcpy()s resp->len bytes from a remote NFC-F device response into the NFCSENSFRESMAXSIZE-byte target.sensfres field without an upper-bound…
When was CVE-2026-80803 disclosed?
CVE-2026-80803 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-80803 actively exploited?
CVE-2026-80803 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 90.5% of all scored CVEs.
How do I remediate CVE-2026-80803?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80803, 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-80803

Explore →

Is Your Infrastructure Affected by CVE-2026-80803?

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

Start Free Scan →Browse All CVEs