mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Hui Peng <benquike@gmail.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipmr: validate IPv4 header length in reg_vif_xmit() and zero iphdr in ipmr_get_route()
Date: Sat, 19 Sep 2026 15:26:35 -0700	[thread overview]
Message-ID: <20260919152635.77563149@kernel.org> (raw)
In-Reply-To: <20260919221737.3708462-1-benquike@gmail.com>

On Sat, 19 Sep 2026 22:17:37 +0000 Hui Peng wrote:
> Fix two bugs in IPv4 multicast routing:
> 
> 1. In reg_vif_xmit() (net/ipv4/ipmr.c), verify that the skb contains a
>    full IPv4 header with ihl >= 5 before reading ip_hdr(skb) and passing
>    the encapsulated PIM register packet to ipmr_cache_report().
> 2. In ipmr_get_route() and inet_rtm_getroute() (net/ipv4/route.c), zero-
>    initialize the synthetic IPv4 header pushed onto the RTM_GETROUTE
>    probe skb so uninitialized slab bytes in iph->ihl / iph->tos /
>    iph->frag_off do not corrupt fib_multipath_hash() or
>    ipmr_cache_alloc().
> 
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Assisted-by: LLM
> Signed-off-by: Hui Peng <benquike@gmail.com>

Stop sending patches right now..

Please wait for feedback on patches you already sent before posting
_anything_ else.

You are allowed to send _revisions_ (new versions) of patches you
already submitted, but since you violated community guidelines by
dumping 40 patches at once you must not post any new networking
patch for the next two months.

Please *think* before you do things :/
-- 
pv-ban: 2mo

  reply	other threads:[~2026-09-19 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 22:17 Hui Peng
2026-09-19 22:26 ` Jakub Kicinski [this message]
2026-09-20 22:18 ` netdev-bot+sashiko

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=20260919152635.77563149@kernel.org \
    --to=kuba@kernel.org \
    --cc=benquike@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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

all inboxes | Powered by JetHome®