From: Kuniyuki Iwashima <kuni1840@gmail.com>
To: rafalbilkowski@gmail.com
Cc: alex.aring@gmail.com, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH] ipv6: ndisc: fix potential out-of-bounds read in ndisc_router_discovery()
Date: Mon, 2 Jun 2025 14:32:35 -0700 [thread overview]
Message-ID: <20250602213310.2519903-1-kuni1840@gmail.com> (raw)
In-Reply-To: <20250602065826.168402-1-rafalbilkowski@gmail.com>
From: Rafal Bilkowski <rafalbilkowski@gmail.com>
Date: Mon, 2 Jun 2025 08:58:26 +0200
> This patch adds a length check at the start of ndisc_router_discovery()
I think it already has the check.
---8<---
optlen = (skb_tail_pointer(skb) - skb_transport_header(skb)) -
sizeof(struct ra_msg);
...
if (optlen < 0)
return SKB_DROP_REASON_PKT_TOO_SMALL;
---8<---
> to prevent a potential out-of-bounds read if a short packet is received.
> Without this check, the function may dereference memory outside the
> buffer.
Do you have a KMSAM splat ?
>
> Fixes: 8610c7c6e3bd ("net: ipv6: add support for rpl sr exthdr")
> Signed-off-by: Rafal Bilkowski <rafalbilkowski@gmail.com>
> ---
> net/ipv6/ndisc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
> index 8d853971f2f6..bdaac5a195d6 100644
> --- a/net/ipv6/ndisc.c
> +++ b/net/ipv6/ndisc.c
> @@ -1235,6 +1235,10 @@ static void ndisc_ra_useropt(struct sk_buff *ra, struct nd_opt_hdr *opt)
>
> static enum skb_drop_reason ndisc_router_discovery(struct sk_buff *skb)
> {
> + // Check if the buffer contains enough data for the struct ra_msg
> + if (!pskb_may_pull(skb, skb_transport_offset(skb) + sizeof(struct ra_msg)))
> + return SKB_DROP_REASON_PKT_TOO_SMALL;
Please run checkpatch.pl. We don't add code before variable declarations.
Also, the skb is linearized in ndisc_rcv().
> +
> struct ra_msg *ra_msg = (struct ra_msg *)skb_transport_header(skb);
> bool send_ifinfo_notify = false;
> struct neighbour *neigh = NULL;
> --
> 2.43.0
prev parent reply other threads:[~2025-06-02 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 6:58 [PATCH] ipv6: ndisc: fix potential out-of-bounds read in ndisc_router_discovery() Rafal Bilkowski
2025-06-02 21:32 ` Kuniyuki Iwashima [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=20250602213310.2519903-1-kuni1840@gmail.com \
--to=kuni1840@gmail.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafalbilkowski@gmail.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