From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>, Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
syzbot+c13a57c2639c2c0d03a6@syzkaller.appspotmail.com
Subject: Re: [PATCH net] ipv4: icmp: reject broadcast/multicast routes
Date: Tue, 19 May 2026 16:30:00 -0600 [thread overview]
Message-ID: <1b2e20b0-63b4-403b-841b-d261bbf358d5@kernel.org> (raw)
In-Reply-To: <20260519200836.4141061-1-edumazet@google.com>
On 5/19/26 2:08 PM, Eric Dumazet wrote:
> syzbot was able to trigger ip_rt_bug() in a loop, using an IPv4 packet
> with a crafted IPOPT_SSRR option:
>
> options: ipv4_options {
> options: array[ipv4_option] {
> union ipv4_option {
> ssrr: ipv4_option_route[IPOPT_SSRR] {
> type: const = 0x89 (1 bytes)
> length: len = 0x7 (1 bytes)
> pointer: int8 = 0xa2 (1 bytes)
> data: array[ipv4_addr] {
> union ipv4_addr {
> broadcast: const = 0xffffffff (4 bytes)
> }
> }
> }
> }
>
> Change __icmp_send() to not send ICMP to broadcast/multicast destinations.
>
> Fixes: c378a9c019cf ("ipv4: Give backtrace in ip_rt_bug().")
> Reported-by: syzbot+c13a57c2639c2c0d03a6@syzkaller.appspotmail.com
> Closes: https://lore.kernel.org/netdev/6a0cc169.170a0220.1f6c2d.0004.GAE@google.com/T/#u
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> net/ipv4/icmp.c | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
prev parent reply other threads:[~2026-05-19 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 20:08 [PATCH net] ipv4: icmp: reject broadcast/multicast routes Eric Dumazet
2026-05-19 22:30 ` David Ahern [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=1b2e20b0-63b4-403b-841b-d261bbf358d5@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+c13a57c2639c2c0d03a6@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