CVE-2026-80802

nfc: fdp: bound the device-reported read length and fix an skb leak

N/A
Published: September 4, 2026 at 03:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.4a06347c04c13e380afce0c9816df51f00b83faf1
Vendor states this is fixed in 0d723090645b82c1cb27cfd7ebf81f0e7c96bcae (fixed)
Vendor states this is fixed in 1aa3fc769b0c45bd19f8dab1697084c2b3f6d706 (fixed)
Vendor states this is fixed in 1fc32327b927a6e2cde086f82575c29880844228 (fixed)
Vendor states this is fixed in 7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1 (fixed)
Vendor states this is fixed in 8d2c243b79854628ff076c38748c020042f02f57 (fixed)
Vendor states this is fixed in d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee (fixed)
Vendor states this is fixed in db7e464b350969c6ea8340de00d9796e5fd5123b (fixed)
Vendor states this is fixed in e5eec121f2c3bc4c7022613bedd9121a8aa4c949 (fixed)
Vendor states this is fixed in fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463 (fixed)
Vendor states this is fixed in 4.4 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card