From: Paolo Abeni <pabeni@redhat.com>
To: Oliver Neukum <oneukum@suse.com>,
dmitry.bezrukov@aquantia.com, marcinguy@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCHv2] USB: gl620a: check for rx buffer overflow
Date: Tue, 05 Dec 2023 09:04:11 +0100 [thread overview]
Message-ID: <73ef03a1607f221c7939cb0646c17c5435dcecd1.camel@redhat.com> (raw)
In-Reply-To: <20231122095306.15175-1-oneukum@suse.com>
On Wed, 2023-11-22 at 10:52 +0100, Oliver Neukum wrote:
> The driver checks for a single package overflowing
> maximum size. That needs to be done, but it is not
> enough. As a single transmission can contain a high
> number of packets, we also need to check whether
> the aggregate of messages in itself short enough
> overflow the buffer.
> That is easiest done by checking that the current
> packet does not overflow the buffer.
>
> Signed-off-by: Oliver Neukum <oneukum@suse.com>
This looks like a bugfix, so a suitable Fixes tag should be included.
> ---
>
> v2: corrected typo in commit message
>
> drivers/net/usb/gl620a.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/net/usb/gl620a.c b/drivers/net/usb/gl620a.c
> index 46af78caf457..d33ae15abdc1 100644
> --- a/drivers/net/usb/gl620a.c
> +++ b/drivers/net/usb/gl620a.c
> @@ -104,6 +104,10 @@ static int genelink_rx_fixup(struct usbnet *dev, struct sk_buff *skb)
> return 0;
> }
>
> + /* we also need to check for overflowing the buffer */
> + if (size > skb->len)
> + return 0;
I think the above is not strict enough: at this point skb->data points
to the gl_packet header. The first 4 bytes in skb are gl_packet-
>packet_length. To ensure an overflow is avoided you should check for:
if (size + 4 > skb->len)
likely with a describing comment.
Cheers,
Paolo
next prev parent reply other threads:[~2023-12-05 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 9:52 [PATCHv2] USB: gl620a: check for rx buffer overflow Oliver Neukum
2023-11-22 9:55 ` Sergey Shtylyov
2023-11-22 10:04 ` Oliver Neukum
2023-11-22 10:07 ` Sergei Shtylyov
2023-11-22 10:20 ` Oliver Neukum
2023-11-24 11:53 ` Simon Horman
2023-11-30 9:38 ` Oliver Neukum
2023-11-30 16:42 ` Simon Horman
2023-12-05 8:04 ` Paolo Abeni [this message]
2023-12-05 10:21 ` Oliver Neukum
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=73ef03a1607f221c7939cb0646c17c5435dcecd1.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dmitry.bezrukov@aquantia.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcinguy@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
/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