CVE-2026-80802
CVE CVE-2026-80802EUVD EUVD-2026-71237Published 2026-09-04T15:13:16.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux a06347c04c13e380afce0c9816df51f00b83faf1 <7ad21dcfeb5181af0c3ee2608808c0c0a5283aa1; patch: 7.3-rc1; patch: 0; patch: 5.10.267; 4.4; a06347c04c13e380afce0c9816df51f00b83faf1 <d9498ab9a78cb63d78dbe4f221d8cc6c91f285ee; a06347c04c13e380afce0c9816df51f00b83faf1 <8d2c243b79854628ff076c38748c020042f02f57; a06347c04c13e380afce0c9816df51f00b83faf1 <db7e464b350969c6ea8340de00d9796e5fd5123b; patch: 6.12.106; patch: 7.1.11; a06347c04c13e380afce0c9816df51f00b83faf1 <1fc32327b927a6e2cde086f82575c29880844228; a06347c04c13e380afce0c9816df51f00b83faf1 <1aa3fc769b0c45bd19f8dab1697084c2b3f6d706; a06347c04c13e380afce0c9816df51f00b83faf1 <e5eec121f2c3bc4c7022613bedd9121a8aa4c949; patch: 6.1.185; patch: 7.2.1; a06347c04c13e380afce0c9816df51f00b83faf1 <fc3c2bd5b1ec6c7cbc8a50e32d9bcec114f25463; a06347c04c13e380afce0c9816df51f00b83faf1 <0d723090645b82c1cb27cfd7ebf81f0e7c96bcae; patch: 5.15.218; patch: 6.6.154; patch: 6.18.47
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.