CVE-2026-80802
nfc: fdp: bound the device-reported read length and fix an skb leak
No known exploitation. EPSS puts it in the 9th percentile. Fixed versions are out.
No public exploit knownFix1 product4 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.1.10.2026.0506
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ a06347c04c13e380afce0c9816df51f00b83faf1, < d9498ab9a78cb63d78dbe4f221d8cc6c91f285eeUpgrade to: d9498ab9a78cb63d78dbe4f221d8cc6c91f285eeAffected: ≥ a06347c04c13e380afce0c9816df51f00b83faf1, < 1fc32327b927a6e2cde086f82575c29880844228Upgrade to: 1fc32327b927a6e2cde086f82575c29880844228Affected: ≥ a06347c04c13e380afce0c9816df51f00b83faf1, < 8d2c243b79854628ff076c38748c020042f02f57Upgrade to: 8d2c243b79854628ff076c38748c020042f02f57Affected: ≥ a06347c04c13e380afce0c9816df51f00b83faf1, < fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463Upgrade to: fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463 + 5 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 9th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 45 days, from the signal feeds we watch.
- Record updated
- OpenVAS check added
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee
- git.kernel.org/stable/c/1fc32327b927a6e2cde086f82575c29880844228
- git.kernel.org/stable/c/8d2c243b79854628ff076c38748c020042f02f57
And 6 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI