From: Brian Norris <briannorris@chromium.org>
To: Pin-yen Lin <treapking@chromium.org>
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>,
Polaris Pi <pinkperfect2021@gmail.com>,
Matthew Wang <matthewmwang@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet
Date: Wed, 13 Sep 2023 13:31:09 -0700 [thread overview]
Message-ID: <ZQIcDWKrmgoPkwlN@google.com> (raw)
In-Reply-To: <20230908104308.1546501-1-treapking@chromium.org>
On Fri, Sep 08, 2023 at 06:41:12PM +0800, Pin-yen Lin wrote:
> Only skip the code path trying to access the rfc1042 headers when the
> buffer is too small, so the driver can still process packets without
> rfc1042 headers.
>
> Fixes: 119585281617 ("wifi: mwifiex: Fix OOB and integer underflow when rx packets")
> Signed-off-by: Pin-yen Lin <treapking@chromium.org>
I'd appreciate another review/test from one of the others here
(Matthew?), even though I know y'all are already working together.
> ---
>
> Changes in v3:
> - Really apply the sizeof call fix as it was missed in the previous patch
>
> Changes in v2:
> - Fix sizeof call (sizeof(rx_pkt_hdr) --> sizeof(*rx_pkt_hdr))
>
> drivers/net/wireless/marvell/mwifiex/sta_rx.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/wireless/marvell/mwifiex/sta_rx.c b/drivers/net/wireless/marvell/mwifiex/sta_rx.c
> index 65420ad67416..257737137cd7 100644
> --- a/drivers/net/wireless/marvell/mwifiex/sta_rx.c
> +++ b/drivers/net/wireless/marvell/mwifiex/sta_rx.c
> @@ -86,7 +86,8 @@ int mwifiex_process_rx_packet(struct mwifiex_private *priv,
> rx_pkt_len = le16_to_cpu(local_rx_pd->rx_pkt_length);
> rx_pkt_hdr = (void *)local_rx_pd + rx_pkt_off;
>
> - if (sizeof(*rx_pkt_hdr) + rx_pkt_off > skb->len) {
> + if (sizeof(rx_pkt_hdr->eth803_hdr) + sizeof(rfc1042_header) +
> + rx_pkt_off > skb->len) {
> mwifiex_dbg(priv->adapter, ERROR,
> "wrong rx packet offset: len=%d, rx_pkt_off=%d\n",
> skb->len, rx_pkt_off);
> @@ -95,12 +96,13 @@ int mwifiex_process_rx_packet(struct mwifiex_private *priv,
> return -1;
> }
>
> - if ((!memcmp(&rx_pkt_hdr->rfc1042_hdr, bridge_tunnel_header,
> - sizeof(bridge_tunnel_header))) ||
> - (!memcmp(&rx_pkt_hdr->rfc1042_hdr, rfc1042_header,
> - sizeof(rfc1042_header)) &&
> - ntohs(rx_pkt_hdr->rfc1042_hdr.snap_type) != ETH_P_AARP &&
> - ntohs(rx_pkt_hdr->rfc1042_hdr.snap_type) != ETH_P_IPX)) {
> + if (sizeof(*rx_pkt_hdr) + rx_pkt_off <= skb->len &&
Are you sure you want this length check to fall back to the non-802.3
codepath? Isn't it an error to look like an 802.3 frame but to be too
small? I'd think we want to drop such packets, not process them as-is.
If I'm correct, then this check should move inside the 'if' branch of
this if/else.
Brian
> + ((!memcmp(&rx_pkt_hdr->rfc1042_hdr, bridge_tunnel_header,
> + sizeof(bridge_tunnel_header))) ||
> + (!memcmp(&rx_pkt_hdr->rfc1042_hdr, rfc1042_header,
> + sizeof(rfc1042_header)) &&
> + ntohs(rx_pkt_hdr->rfc1042_hdr.snap_type) != ETH_P_AARP &&
> + ntohs(rx_pkt_hdr->rfc1042_hdr.snap_type) != ETH_P_IPX))) {
> /*
> * Replace the 803 header and rfc1042 header (llc/snap) with an
> * EthernetII header, keep the src/dst and snap_type
> --
> 2.42.0.283.g2d96d420d3-goog
>
next prev parent reply other threads:[~2023-09-13 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 10:41 [PATCH v3] wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet Pin-yen Lin
2023-09-13 20:31 ` Brian Norris [this message]
2023-09-14 7:09 ` Pin-yen Lin
2023-09-14 23:38 ` Brian Norris
2023-09-18 7:50 ` Matthew Wang
2023-09-18 13:06 ` Kalle Valo
2023-09-18 13:19 ` Kalle Valo
2023-09-19 12:31 ` Matthew Wang
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=ZQIcDWKrmgoPkwlN@google.com \
--to=briannorris@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthewmwang@chromium.org \
--cc=pinkperfect2021@gmail.com \
--cc=treapking@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).