From: patchwork-bot+netdevbpf@kernel.org
To: Yochai Eisenrich <echelonh@gmail.com>
Cc: davem@davemloft.net, dsahern@kernel.org, security@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak
Date: Fri, 27 Mar 2026 03:50:08 +0000 [thread overview]
Message-ID: <177458340854.3291104.1692418192730790806.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260324224925.2437775-1-echelonh@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 25 Mar 2026 00:49:25 +0200 you wrote:
> When processing Router Advertisements with user options the kernel
> builds an RTM_NEWNDUSEROPT netlink message. The nduseroptmsg struct
> has three padding fields that are never zeroed and can leak kernel data
>
> The fix is simple, just zeroes the padding fields.
>
> Fixes: 31910575a9de ("[IPv6]: Export userland ND options through netlink
> (RDNSS support)")
> Signed-off-by: Yochai Eisenrich <echelonh@gmail.com>
>
> [...]
Here is the summary with links:
- net: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak
https://git.kernel.org/netdev/net/c/ae05340ccaa9
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-03-27 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 22:49 [PATCH] net: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak Yochai Eisenrich
2026-03-26 20:14 ` Simon Horman
2026-03-27 3:50 ` 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=177458340854.3291104.1692418192730790806.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=echelonh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=security@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