From: patchwork-bot+netdevbpf@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: security@kernel.org, edumazet@google.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
xmei5@asu.edu
Subject: Re: [PATCH net] icmp: fix NULL pointer dereference in icmp_tag_validation()
Date: Thu, 19 Mar 2026 16:40:08 +0000 [thread overview]
Message-ID: <177393840804.1701817.18293524741667806586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260318130558.1050247-4-bestswngs@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 18 Mar 2026 21:06:01 +0800 you wrote:
> From: Weiming Shi <bestswngs@gmail.com>
>
> icmp_tag_validation() unconditionally dereferences the result of
> rcu_dereference(inet_protos[proto]) without checking for NULL.
> The inet_protos[] array is sparse -- only about 15 of 256 protocol
> numbers have registered handlers. When ip_no_pmtu_disc is set to 3
> (hardened PMTU mode) and the kernel receives an ICMP Fragmentation
> Needed error with a quoted inner IP header containing an unregistered
> protocol number, the NULL dereference causes a kernel panic in
> softirq context.
>
> [...]
Here is the summary with links:
- [net] icmp: fix NULL pointer dereference in icmp_tag_validation()
https://git.kernel.org/netdev/net/c/614aefe56af8
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-19 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 13:06 [PATCH net] icmp: fix NULL pointer dereference in icmp_tag_validation() bestswngs
2026-03-19 16:40 ` 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=177393840804.1701817.18293524741667806586.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bestswngs@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@kernel.org \
--cc=xmei5@asu.edu \
/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