From: Yuran Pereira <yuran.pereira@hotmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
florian.fainelli@broadcom.com, linux-kernel@vger.kernel.org,
justin.chen@broadcom.com, edumazet@google.com,
bcm-kernel-feedback-list@broadcom.com, kuba@kernel.org,
pabeni@redhat.com,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] Prevent out-of-bounds read/write in bcmasp_netfilt_rd and bcmasp_netfilt_wr
Date: Fri, 3 Nov 2023 19:12:57 +0530 [thread overview]
Message-ID: <DB3PR10MB68352DF6CB458CCF97C416ECE8A5A@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <2023110301-purist-reputable-fab7@gregkh>
Hello Greg,
On Fri, Nov 03, 2023 at 01:57:13PM +0100, Greg KH wrote:
> > reg_offset = bcmasp_netfilt_get_reg_offset(priv, nfilt, reg_type,
> > offset);
> > + if (reg_offset < 0)
> > + return 0;
>
> Shouldn't you return an error here?
Yes, I think that makes sense. I might just return `reg_offset`
since it is bound to be -EINVAL when bcmasp_netfilt_get_reg_offset
fails.
But that now makes me wonder whether the previous check in that
function which currently returns 0, shouldn't be returning `-EINVAL`
instead.
```
static u32 bcmasp_netfilt_rd(struct bcmasp_priv *priv,
...
{
if (!IS_ALIGNED(offset, 4) || offset > MAX_WAKE_FILTER_SIZE)
return 0; <----- Should this one be -EINVAL?
}
```
Thank you for the feedback.
Yuran
next prev parent reply other threads:[~2023-11-03 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 12:27 Yuran Pereira
2023-11-03 12:57 ` Greg KH
2023-11-03 13:42 ` Yuran Pereira [this message]
2023-11-03 14:14 ` Yuran Pereira
2023-11-03 14:19 ` Yuran Pereira
2023-11-03 18:23 ` Justin Chen
2023-11-03 18:33 ` Greg KH
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=DB3PR10MB68352DF6CB458CCF97C416ECE8A5A@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM \
--to=yuran.pereira@hotmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=justin.chen@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®