From: David Ahern <dsahern@kernel.org>
To: Gavrilov Ilia <Ilia.Gavrilov@infotecs.ru>,
"David S. Miller" <davem@davemloft.net>
Cc: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Vlad Yasevich <vyasevic@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>
Subject: Re: [PATCH net] ipv6: Fix out-of-bounds access in ipv6_find_tlv()
Date: Tue, 23 May 2023 09:21:41 -0600 [thread overview]
Message-ID: <36eea968-d3e8-fc1e-6d88-0f19fce130d8@kernel.org> (raw)
In-Reply-To: <20230523082903.117626-1-Ilia.Gavrilov@infotecs.ru>
On 5/23/23 2:29 AM, Gavrilov Ilia wrote:
> optlen is fetched without checking whether there is more than one byte to parse.
> It can lead to out-of-bounds access.
>
> Found by InfoTeCS on behalf of Linux Verification Center
> (linuxtesting.org) with SVACE.
>
> Fixes: 3c73a0368e99 ("ipv6: Update ipv6 static library with newly needed functions")
That is not the right Fixes tag; that commit only moved the code.
Fixes: c61a40432509 ("[IPV6]: Find option offset by type.")
> Signed-off-by: Gavrilov Ilia <Ilia.Gavrilov@infotecs.ru>
> ---
> net/ipv6/exthdrs_core.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/net/ipv6/exthdrs_core.c b/net/ipv6/exthdrs_core.c
> index da46c4284676..49e31e4ae7b7 100644
> --- a/net/ipv6/exthdrs_core.c
> +++ b/net/ipv6/exthdrs_core.c
> @@ -143,6 +143,8 @@ int ipv6_find_tlv(const struct sk_buff *skb, int offset, int type)
> optlen = 1;
> break;
> default:
> + if (len < 2)
> + goto bad;
> optlen = nh[offset + 1] + 2;
> if (optlen > len)
> goto bad;
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-05-23 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 8:29 [PATCH net] ipv6: Fix out-of-bounds access in ipv6_find_tlv() Gavrilov Ilia
2023-05-23 13:26 ` Jiri Pirko
2023-05-23 15:21 ` David Ahern [this message]
2023-05-24 7:50 ` patchwork-bot+netdevbpf
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=36eea968-d3e8-fc1e-6d88-0f19fce130d8@kernel.org \
--to=dsahern@kernel.org \
--cc=Ilia.Gavrilov@infotecs.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vyasevic@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