[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <65e53548-2d68-464a-87bd-909f360cdb1c@redhat.com>
Date: Tue, 30 Sep 2025 11:57:07 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Guangshuo Li <lgs201920130244@...il.com>, Krzysztof Halasa
<khc@...waw.pl>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: stable@...r.kernel.org
Subject: Re: [PATCH] net: wan: hd64572: validate RX length before skb
allocation and copy
On 9/26/25 12:49 PM, Guangshuo Li wrote:
> The driver trusts the RX descriptor length and uses it directly for
> dev_alloc_skb(), memcpy_fromio(), and skb_put() without any bounds
> checking. If the descriptor gets corrupted or otherwise contains an
> invalid value,
Why/how? Is the H/W known to corrupt the descriptors? If so please point
that out in the commit message.
Otherwise, if this is intended to protect vs generic memory corruption
inside the kernel caused by S/W bug, please look for such corruption
root cause instead.
Thanks,
Paolo
Powered by blists - more mailing lists