linux-kernel - [Bug] "soft lockup in corrupted" in Linux Kernel v6.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAP=Rh=NB1bAs9Rn+cf8LPBUtStsHOF==9W89gyvuO=q7Cmrpug@mail.gmail.com>
Date: Wed, 21 May 2025 21:34:15 +0800
From: John <john.cs.hey@...il.com>
To: Josh Poimboeuf <jpoimboe@...nel.org>, Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, 
	Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org, 
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: [Bug] "soft lockup in corrupted" in Linux Kernel v6.14

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: arch_stack_walk+0x79/0xf0 in arch/x86/kernel/stacktrace.c:27

Bug report: https://pastebin.com/6yUV9ssn

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

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

Root Cause Analysis:
A soft lockup occurred on CPU#1 in the arch_stack_walk() function
during an interrupt context (<IRQ>), while the kernel was trying to
walk the stack.
This call chain ultimately intersected with the RCU callback execution
(rcu_do_batch() → kfree()), and KASAN instrumentation code, which led
to extensive CPU spinning in an interrupt context without yielding,
triggering the soft lockup detector.

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