Linux wireless drivers development
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@gmail.com>
To: Xiang Mei <xmei5@asu.edu>, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Johannes Berg <johannes.berg@intel.com>,
	Arien Judge <arien.judge@morsemicro.com>,
	Lachlan Hodges <lachlan.hodges@morsemicro.com>,
	Weiming Shi <bestswngs@gmail.com>
Subject: Re: [PATCH wireless] wifi: p54: validate RX frame length in p54_rx_eeprom_readback()
Date: Sat, 4 Jul 2026 22:08:43 +0200	[thread overview]
Message-ID: <80d10637-2654-4dd6-bb24-3fbada3aa801@gmail.com> (raw)
In-Reply-To: <20260628000510.4152481-1-xmei5@asu.edu>

On 6/28/26 2:05 AM, Xiang Mei wrote:
> 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.
> 
> Fixes: 7cb770729ba8 ("p54: move eeprom code into common library")

Sure

Acked-by: Christian Lamparter <chunkeey@gmail.com>

> Reported-by: Weiming Shi <bestswngs@gmail.com>
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Xiang Mei <xmei5@asu.edu>
> ---
>   drivers/net/wireless/intersil/p54/txrx.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/net/wireless/intersil/p54/txrx.c b/drivers/net/wireless/intersil/p54/txrx.c
> index 1294a1d6528e..9f491334c8d0 100644
> --- a/drivers/net/wireless/intersil/p54/txrx.c
> +++ b/drivers/net/wireless/intersil/p54/txrx.c
> @@ -499,11 +499,19 @@ static void p54_rx_eeprom_readback(struct p54_common *priv,
>   		if (le16_to_cpu(eeprom->v2.len) != priv->eeprom_slice_size)
>   			return;
>   
> +		if (eeprom->v2.data + priv->eeprom_slice_size >
> +		    skb_tail_pointer(skb))
> +			return;
> +
>   		memcpy(priv->eeprom, eeprom->v2.data, priv->eeprom_slice_size);
>   	} else {
>   		if (le16_to_cpu(eeprom->v1.len) != priv->eeprom_slice_size)
>   			return;
>   
> +		if (eeprom->v1.data + priv->eeprom_slice_size >
> +		    skb_tail_pointer(skb))
> +			return;
> +
>   		memcpy(priv->eeprom, eeprom->v1.data, priv->eeprom_slice_size);
>   	}
>   


      reply	other threads:[~2026-07-04 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28  0:05 [PATCH wireless] wifi: p54: validate RX frame length in p54_rx_eeprom_readback() Xiang Mei
2026-07-04 20:08 ` Christian Lamparter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80d10637-2654-4dd6-bb24-3fbada3aa801@gmail.com \
    --to=chunkeey@gmail.com \
    --cc=arien.judge@morsemicro.com \
    --cc=bestswngs@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=lachlan.hodges@morsemicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=xmei5@asu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox