CVE Catalog

CVE-2026-80802

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel NFC subsystem for FDP (NXP) controllers, the fdp_nci_i2c_read() function takes the next packet length from two device-supplied bytes and never validates it. This can lead to a stack out-of-bounds write or an skb leak in case of a faulty device. The fix rejects lengths outside the allowed range and frees a previously allocated skb before allocating the next.

Risk Assessment

The risk includes potential remote code execution or system crash via a connected malicious or malfunctioning NFC device. This could lead to system integrity compromise or DoS attack.

Recommendation

It is recommended to urgently apply the official Linux kernel patch. Also avoid connecting untrusted NFC devices to critical systems.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS