The Linux Kernel Mailing List
 help / color / mirror / Atom feed
* [Bug] "WARNING in should_fail_ex" in Linux kernel v6.14
@ 2025-05-21 14:13 John
  2025-05-21 18:50 ` Kuniyuki Iwashima
  0 siblings, 1 reply; 2+ messages in thread
From: John @ 2025-05-21 14:13 UTC (permalink / raw)
  To: David S. Miller, David Ahern, Eric Dumazet, Jakub Kicinski,
	Paolo Abeni
  Cc: Simon Horman, netdev, linux-kernel

Dear Linux Kernel Maintainers,

I hope this message finds you well.

I am writing to report a potential vulnerability I encountered during
testing of the Linux Kernel version v6.14.

Git Commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557 (tag: v6.14)

Bug Location: net/ipv4/ipmr.c:440 ipmr_free_table net/ipv4/ipmr.c:440

Bug report: https://pastebin.com/xkfF5DBt

Complete log: https://pastebin.com/uCfqY4D8

Entire kernel config: https://pastebin.com/MRWGr3nv

Root Cause Analysis:
The kernel warning is triggered in ipmr_free_table() at
net/ipv4/ipmr.c:440, where the multicast routing table (mr_table) is
being freed during network namespace exit (ipmr_rules_exit).
The warning indicates that the multicast forwarding cache count
(mfc_cache_cnt) is non-zero, implying that resources were not
correctly cleaned up prior to netns teardown.
This suggests a possible bug in reference counting or teardown logic
of the IPv4 multicast routing infrastructure.
Additionally, the environment is running with fail_usercopy fault
injection enabled, which deliberately triggers copy-from-user failures
to test kernel error paths.
While these failures are expected, they may interact with multicast
socket setup/teardown paths, exacerbating latent issues.

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.

Best regards,
John

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Bug] "WARNING in should_fail_ex" in Linux kernel v6.14
  2025-05-21 14:13 [Bug] "WARNING in should_fail_ex" in Linux kernel v6.14 John
@ 2025-05-21 18:50 ` Kuniyuki Iwashima
  0 siblings, 0 replies; 2+ messages in thread
From: Kuniyuki Iwashima @ 2025-05-21 18:50 UTC (permalink / raw)
  To: john.cs.hey
  Cc: davem, dsahern, edumazet, horms, kuba, linux-kernel, netdev,
	pabeni

From: John <john.cs.hey@gmail.com>
Date: Wed, 21 May 2025 22:13:15 +0800
> Dear Linux Kernel Maintainers,
> 
> I hope this message finds you well.
> 
> I am writing to report a potential vulnerability I encountered during
> testing of the Linux Kernel version v6.14.
> 
> Git Commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557 (tag: v6.14)
> 
> Bug Location: net/ipv4/ipmr.c:440 ipmr_free_table net/ipv4/ipmr.c:440
> 
> Bug report: https://pastebin.com/xkfF5DBt
> 
> Complete log: https://pastebin.com/uCfqY4D8
> 
> Entire kernel config: https://pastebin.com/MRWGr3nv
> 
> Root Cause Analysis:
> The kernel warning is triggered in ipmr_free_table() at
> net/ipv4/ipmr.c:440, where the multicast routing table (mr_table) is
> being freed during network namespace exit (ipmr_rules_exit).
> The warning indicates that the multicast forwarding cache count
> (mfc_cache_cnt) is non-zero, implying that resources were not
> correctly cleaned up prior to netns teardown.
> This suggests a possible bug in reference counting or teardown logic
> of the IPv4 multicast routing infrastructure.
> Additionally, the environment is running with fail_usercopy fault
> injection enabled, which deliberately triggers copy-from-user failures
> to test kernel error paths.
> While these failures are expected, they may interact with multicast
> socket setup/teardown paths, exacerbating latent issues.

I think this was fixed by

commit c46286fdd6aa1d0e33c245bcffe9ff2428a777bd
Author: Paolo Abeni <pabeni@redhat.com>
Date:   Thu May 15 18:49:26 2025 +0200

    mr: consolidate the ipmr_can_free_table() checks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-05-21 18:50 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-05-21 14:13 [Bug] "WARNING in should_fail_ex" in Linux kernel v6.14 John
2025-05-21 18:50 ` Kuniyuki Iwashima

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox