From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
syoshida@redhat.com, kuni1840@gmail.com, netdev@vger.kernel.org,
syzbot+707d6a5da1ab9e0c6f9d@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] ipv6: Fix out-of-bound access in fib6_add_rt2node().
Date: Fri, 13 Feb 2026 20:30:11 +0000 [thread overview]
Message-ID: <177101461132.2548179.11036881071505557933.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260211175133.3657034-1-kuniyu@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 11 Feb 2026 17:50:21 +0000 you wrote:
> syzbot reported out-of-bound read in fib6_add_rt2node(). [0]
>
> When IPv6 route is created with RTA_NH_ID, struct fib6_info
> does not have the trailing struct fib6_nh.
>
> The cited commit started to check !iter->fib6_nh->fib_nh_gw_family
> to ensure that rt6_qualify_for_ecmp() will return false for iter.
>
> [...]
Here is the summary with links:
- [v1,net] ipv6: Fix out-of-bound access in fib6_add_rt2node().
https://git.kernel.org/netdev/net/c/8244f959e2c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-02-13 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 17:50 [PATCH v1 net] ipv6: Fix out-of-bound access in fib6_add_rt2node() Kuniyuki Iwashima
2026-02-11 19:51 ` Fernando Fernandez Mancera
2026-02-12 9:27 ` Shigeru Yoshida
2026-02-13 20:30 ` patchwork-bot+netdevbpf [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=177101461132.2548179.11036881071505557933.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syoshida@redhat.com \
--cc=syzbot+707d6a5da1ab9e0c6f9d@syzkaller.appspotmail.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