From: Hillf Danton <hdanton@sina.com>
To: Eric Dumazet <edumazet@google.com>
Cc: YAN KANG <kangyan91@outlook.com>, netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: general protection fault in ip6_pol_route
Date: Wed, 5 Feb 2025 19:33:31 +0800 [thread overview]
Message-ID: <20250205113334.1960-1-hdanton@sina.com> (raw)
In-Reply-To: <CANn89iKCqR_wid4+g65Mx6jVTAuqJcKOocMCs09-7J+knSAKoQ@mail.gmail.com>
On Tue, 4 Feb 2025 15:07:49 +0100 Eric Dumazet <edumazet@google.com>
> On Tue, Feb 4, 2025 at 2:47 PM YAN KANG <kangyan91@outlook.com> wrote:
> >
> > Dear maintainers,
> >
> > I found a kernel bug titiled "general protection fault in ip6_pol_route" while using modified syzkaller fuzzing tool. I Itested it on the latest Linux upstream version (6.13.0-rc7) .
> >
> >
> > After preliminary analysis, the rootcause may be in ip6_pol_route function net/ipv6/route.c
> > res is a stack object. [1]
> > fib6_select_path(net, &res, fl6, oif, false, skb, strict) call may initialize res->nh.[2]
> > rt = rt6_get_pcpu_route( &res); [3]
> > pcpu_rt = this_cpu_read(*res->nh->rt6i_pcpu); // *res->nh is NULL, crash
> >
> > in [2], res->nh can be initialized in several ways,possibly one of which initializes it to NULL.
> >
> > Unfortunately, I don't have any reproducer for this bug yet.
> >
> > If you fix this issue, please add the following tag to the commit:
> > Reported-by: yan kang <kangyan91@outlook.com>
> > Reported-by: yue sun <samsun1006219@gmail.com
> >
> This is a dup of a syzbot report under investigation.
>
> Unless you have a repro and/or a patch, I would recommend you not
> sending these fuzzer reports anymore.
>
> Releasing such reports without a fix is an obvious security risk.
>
Can you specify a bit why report like this one links to security risk, Eric,
given no fix yet delivered to the syzbot report [1] so far?
[1] https://yhbt.net/lore/lkml/67a21f26.050a0220.163cdc.0068.GAE@google.com/
prev parent reply other threads:[~2025-02-05 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:47 YAN KANG
2025-02-04 14:07 ` Eric Dumazet
2025-02-05 11:33 ` Hillf Danton [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=20250205113334.1960-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=edumazet@google.com \
--cc=kangyan91@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®