From: Paolo Abeni <pabeni@redhat.com>
To: John <john.cs.hey@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug] "WARNING in corrupted" in Linux Kernel v6.15-rc5
Date: Mon, 26 May 2025 12:48:40 +0200 [thread overview]
Message-ID: <451f45a0-4db4-40a7-ba22-d2a7dd1a1c7d@redhat.com> (raw)
In-Reply-To: <CAP=Rh=MXN2U7ydg2f9k1cywF8Q1qpizXmcBg6mmzwpt86=PaWw@mail.gmail.com>
On 5/26/25 9:11 AM, John wrote:
> I am writing to report a potential vulnerability I encountered during
> testing of the Linux Kernel version v6.15-rc5.
>
> Git Commit: 92a09c47464d040866cf2b4cd052bc60555185fb (tag: v6.15-rc5)
>
> Bug Location: 20628 at net/ipv4/ipmr.c:440 ipmr_free_table
> net/ipv4/ipmr.c:440 [inline]
>
> Bug report: https://hastebin.com/share/idudaveten.yaml
>
> Complete log: https://hastebin.com/share/ojonatucos.perl
>
> Entire kernel config: https://hastebin.com/share/padecilimo.ini
>
> Root Cause Analysis:
> A kernel warning is triggered during the execution of
> ipmr_rules_exit() at line 440 of net/ipv4/ipmr.c, when attempting to
> free a multicast routing (mr) table that may have already been
> released or was never correctly initialized.
> This function is called as part of the ipmr_net_exit_batch() logic
> when a network namespace is being torn down (copy_net_ns() →
> create_new_namespaces() → unshare() syscall).
> The crash is accompanied by a FAULT_INJECTION trace involving
> copy_from_user_iter, suggesting this might be a fuzzing-induced fault
> where the data passed via netlink_sendmsg() is malformed.
> However, the primary issue lies in ipmr_free_table() dereferencing a
> potentially invalid pointer—either due to a race condition during
> namespace teardown or improper error handling during netns
> initialization.
>
> At present, I have not yet obtained a minimal reproducer for this
> issue. However, I am actively working on reproducing it, and I will
> promptly share any additional findings or a working reproducer as soon
> as it becomes available.
>
> Thank you very much for your time and attention to this matter. I
> truly appreciate the efforts of the Linux kernel community.
Should be fixed by commit c46286fdd6aa, which landed in 6.15
/P
prev parent reply other threads:[~2025-05-26 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 7:11 John
2025-05-26 10:48 ` Paolo Abeni [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=451f45a0-4db4-40a7-ba22-d2a7dd1a1c7d@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=john.cs.hey@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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
all inboxes | Powered by JetHome®