wifi: p54: validate RX frame length in p54_rx_eeprom_readback()
Summary
| CVE | CVE-2026-64571 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-05 08:16:36 UTC |
| Updated | 2026-08-05 08:16:36 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate RX frame length in p54_rx_eeprom_readback() p54_rx_eeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit da1b9a55ff11 ("wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()") closed the destination overflow by copying a fixed priv->eeprom_slice_size (and rejecting a mismatched advertised len), but the source side is still unbounded: nothing verifies the frame is long enough to supply that many bytes. A malicious USB device can send a short frame whose advertised len matches priv->eeprom_slice_size while the payload is truncated. The equality check passes and memcpy() reads past the end of the skb, leaking adjacent heap: BUG: KASAN: slab-out-of-bounds in p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) Read of size 1016 at addr ffff88800f077114 by task swapper/0/0 Call Trace: <IRQ> ... __asan_memcpy (mm/kasan/shadow.c:105) p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) p54u_rx_cb (drivers/net/wireless/intersil/p54/p54usb.c:163) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:2005) ... </IRQ> The buggy address belongs to the object at ffff88800f0770c0 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 84 bytes inside of allocated 704-byte region [ffff88800f0770c0, ffff88800f077380) Check that the slice fits in the skb before copying. |
Risk And Classification
EPSS: 0.001560000 probability, percentile 0.052520000 (date 2026-08-09)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 25c3b85af3fc4f8043159b14e65790fc3bbdaf48 git | Not specified |
| CNA | Linux | Linux | affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 f46f8f9c43fd02f4dd5f716d4bda296a523c04f0 git | Not specified |
| CNA | Linux | Linux | affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 d38f5d868a0a4770e3bcd0925e16c46acdbc9509 git | Not specified |
| CNA | Linux | Linux | affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 9096e1f7014174067239a63df18ae5f28301990d git | Not specified |
| CNA | Linux | Linux | affected 7cb770729ba895f73253dfcd46c3fcba45d896f9 ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea git | Not specified |
| CNA | Linux | Linux | affected 2.6.28 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.28 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.148 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.101 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.42 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.6 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2-rc4 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/25c3b85af3fc4f8043159b14e65790fc3bbdaf48 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9096e1f7014174067239a63df18ae5f28301990d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f46f8f9c43fd02f4dd5f716d4bda296a523c04f0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d38f5d868a0a4770e3bcd0925e16c46acdbc9509 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.