nfc: fdp: bound the device-reported read length and fix an skb leak
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Fixed version: Linux Linux 0d723090645b82c1cb27cfd7ebf81f0e7c96bcae, 1aa3fc769b0c45bd19f8dab1697084c2b3f6d706, 1fc32327b927a6e2cde086f82575c29880844228.
Low priority for now. Upgrade to Linux Linux 0d723090645b82c1cb27cfd7ebf81f0e7c96bcae, 1aa3fc769b0c45bd19f8dab1697084c2b3f6d706, 1fc32327b927a6e2cde086f82575c29880844228 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.4affected
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before d9498ab9a78cb63d78dbe4f221d8cc6c91f285eeaffected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before 1fc32327b927a6e2cde086f82575c29880844228affected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before 8d2c243b79854628ff076c38748c020042f02f57affected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463affected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before 0d723090645b82c1cb27cfd7ebf81f0e7c96bcaeaffected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before db7e464b350969c6ea8340de00d9796e5fd5123baffected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before e5eec121f2c3bc4c7022613bedd9121a8aa4c949affected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before 1aa3fc769b0c45bd19f8dab1697084c2b3f6d706affected · git
- a06347c04c13e380afce0c9816df51f00b83faf1 and later · before 7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80800Sep 4, 2026 · nfc: llcp: bound the connect_sn TLV walk to the skb0Monitor
- ← EarlierCVE-2026-80801Sep 4, 2026 · nfc: microread: validate target discovery payload lengths0Monitor
- Later →CVE-2026-80803Sep 4, 2026 · nfc: digital: clamp SENSF_RES length to the destination buffer0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0d723090645b82c1cb27cfd7ebf81f0e7c96bcae | Vendor (CNA) |
| Linux Linux | 1aa3fc769b0c45bd19f8dab1697084c2b3f6d706 | Vendor (CNA) |
| Linux Linux | 1fc32327b927a6e2cde086f82575c29880844228 | Vendor (CNA) |
| Linux Linux | 7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1 | Vendor (CNA) |
| Linux Linux | 8d2c243b79854628ff076c38748c020042f02f57 | Vendor (CNA) |
| Linux Linux | d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee | Vendor (CNA) |
| Linux Linux | db7e464b350969c6ea8340de00d9796e5fd5123b | Vendor (CNA) |
| Linux Linux | e5eec121f2c3bc4c7022613bedd9121a8aa4c949 | Vendor (CNA) |
| Linux Linux | fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/1aa3fc769b0c45bd19f8dab1697084c2b3f6d706
- git.kernel.org/stable/c/1fc32327b927a6e2cde086f82575c29880844228
- git.kernel.org/stable/c/7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1
- git.kernel.org/stable/c/8d2c243b79854628ff076c38748c020042f02f57
- git.kernel.org/stable/c/d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee
- git.kernel.org/stable/c/db7e464b350969c6ea8340de00d9796e5fd5123b
- git.kernel.org/stable/c/e5eec121f2c3bc4c7022613bedd9121a8aa4c949
- git.kernel.org/stable/c/fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463
Vendor advisories and official records. Exploit/PoC links are deliberately left out.