CVE-2026-64571

wifi: p54: validate RX frame length in p54_rx_eeprom_readback()

N/A
Published: August 5, 2026 at 08:08 AM UTC
Updated: August 19, 2026 at 05:20 PM 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: 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.

Affected

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

2.6.28 ≤ v < 5.10.2652.6.28 ≤ v < 5.15.2162.6.28 ≤ v < 6.1.1832.6.28 ≤ v < 6.12.1012.6.28 ≤ v < 6.18.422.6.28 ≤ v < 6.6.1482.6.28 ≤ v < 7.1.62.6.28 ≤ v < 7.22.6.287cb770729ba895f73253dfcd46c3fcba45d896f9
Vendor states this is fixed in 25c3b85af3fc4f8043159b14e65790fc3bbdaf48 (fixed)
Vendor states this is fixed in 7a456ffcd20bd92ad0ef46c1aaa0e39e3be1f7e7 (fixed)
Vendor states this is fixed in 88f7044f92b8326fbfab26d0d8ed297c367ebb76 (fixed)
Vendor states this is fixed in 9096e1f7014174067239a63df18ae5f28301990d (fixed)
Vendor states this is fixed in d38f5d868a0a4770e3bcd0925e16c46acdbc9509 (fixed)
Vendor states this is fixed in ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea (fixed)
Vendor states this is fixed in f21b7e096fe5371bf697cd410537fb434a763f5e (fixed)
Vendor states this is fixed in f46f8f9c43fd02f4dd5f716d4bda296a523c04f0 (fixed)
Vendor states this is fixed in 2.6.28 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (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