CVE-2026-80802 — nfc: fdp: bound the device-reported read length and fix an skb leak
In the Linux kernel, the following vulnerability has been resolved: nfc: fdp: bound the device-reported read length and fix an skb leak fdp_nci_i2c_read() takes the next packet length from two device-supplied bytes and never validates it. The value is a u16 used as the i2c_master_recv() count into a 261-byte on-stack buffer: a malicious, counterfeit or malfunctioning controller (or an i2c bus interposer) can drive it far past the buffer for a stack out-of-bounds write that clobbers the canary and return address, or below the minimum frame size (directly, or by truncating the computed sum) so the header/LRC strip and the next length read run past a short receive. Reject a length outside [FDP_NCI_I2C_MIN_PAYLOAD, FDP_NCI_I2C_MAX_PAYLOAD], as a corrupted packet already is, and force resynchronization. The same loop allocates one data skb per iteration and assumes a length packet followed by a data packet; a device that sends two data packets in one call leaks the first skb when the second allocation overwrites it. Free a previously allocated skb before allocating the next.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < 1fc32327b927a6e2cde086f82575c29880844228≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < 8d2c243b79854628ff076c38748c020042f02f57≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < 0d723090645b82c1cb27cfd7ebf81f0e7c96bcae≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < db7e464b350969c6ea8340de00d9796e5fd5123b≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < e5eec121f2c3bc4c7022613bedd9121a8aa4c949≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < 1aa3fc769b0c45bd19f8dab1697084c2b3f6d706 and 2 more≥ a06347c04c13e380afce0c9816df51f00b83faf1 and < 7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1version 4.4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.24%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/db7e464b350969c6ea8340de00d9796e5fd5123b
- git.kernel.org/stable/c/d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee
- git.kernel.org/stable/c/0d723090645b82c1cb27cfd7ebf81f0e7c96bcae
- git.kernel.org/stable/c/fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463
- nvd.nist.gov/vuln/detail/CVE-2026-80802
- git.kernel.org/stable/c/8d2c243b79854628ff076c38748c020042f02f57
- git.kernel.org/stable/c/e5eec121f2c3bc4c7022613bedd9121a8aa4c949
- github.com/advisories/GHSA-6fmj-x4q6-pp6w
- git.kernel.org/stable/c/1fc32327b927a6e2cde086f82575c29880844228
- git.kernel.org/stable/c/7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1
- git.kernel.org/stable/c/1aa3fc769b0c45bd19f8dab1697084c2b3f6d706
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 14h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 14h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 14h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 14h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 14h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 14h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80802 is "nfc: fdp: bound the device-reported read length and fix an skb leak", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.