mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Eric Dumazet <edumazet@google.com>, Luka <luka.2016.cs@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug] soft lockup in neigh_timer_handler in Linux kernel v6.12
Date: Wed, 9 Jul 2025 09:06:26 +0200	[thread overview]
Message-ID: <da0f1340-34c5-4932-953e-25cad641db87@kernel.org> (raw)
In-Reply-To: <CANn89i+7m8koanZk=47FEhmTHUmOmu-yfViRPayjUct+voQiEQ@mail.gmail.com>

On 08/07/2025 10:02, Eric Dumazet wrote:
> On Tue, Jul 8, 2025 at 12:54 AM Luka <luka.2016.cs@gmail.com> wrote:
>>
>> 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.12.
>>
>> Git Commit: adc218676eef25575469234709c2d87185ca223a (tag: v6.12)
>>
>> Bug Location: neigh_timer_handler+0xc17/0xfe0 net/core/neighbour.c:1148
>>
>> Bug report: https://pastebin.com/06NiBtXm
>>
>> Entire kernel config: https://pastebin.com/MRWGr3nv
>>
>> Root Cause Analysis:
>>
>> A soft lockup occurs in the neighbor subsystem due to prolonged
>> execution within neigh_timer_handler(), where repeated neighbor entry
>> invalidation and associated routing operations (e.g.,
>> ipv4_link_failure() and arp_error_report()) lead to excessive CPU
>> occupation without yielding, triggering the kernel watchdog.
>>
>> 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.
> 
> Please stop sending duplicates, and 'analysis' AI generated.
> 
> If you really want to help, please provide a patch.


That's the same person which before was sending fake reports, based on
AI hallucination. Just in case - don't waste any time in reading the
reports.

Best regards,
Krzysztof

      reply	other threads:[~2025-07-09  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  7:54 Luka
2025-07-08  8:02 ` Eric Dumazet
2025-07-09  7:06   ` Krzysztof Kozlowski [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=da0f1340-34c5-4932-953e-25cad641db87@kernel.org \
    --to=krzk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luka.2016.cs@gmail.com \
    --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®