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=NewbpXABhEECGAfBaA_1XtijWDhrainjuKZc6WYXrQZg@mail.gmail.com>
Date: Fri, 23 May 2025 09:10:17 +0800
From: John <john.cs.hey@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, linux-kernel@...r.kernel.org, 
	linux-trace-kernel@...r.kernel.org
Subject: [Bug] "soft lockup in inet6_release“ in Linux Kernel v6.15-rc5

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.15-rc5.

Git Commit: 92a09c47464d040866cf2b4cd052bc60555185fb (tag: v6.15-rc5)

Bug Location: 0010:perf_trace_buf_update+0x19/0x190
kernel/trace/trace_event_perf.c:429

Bug report: https://hastebin.com/share/udusequyew.bash

Complete log: https://hastebin.com/share/ibalexehon.perl

Entire kernel config: https://hastebin.com/share/padecilimo.ini

Root Cause Analysis:
A soft lockup was detected on CPU#0 with the instruction pointer (RIP)
stuck in the perf_trace_buf_update() function (at
kernel/trace/trace_event_perf.c:429).
This function was invoked indirectly as part of the inet6_release()
socket cleanup path, during the final phase of socket destruction
(__sk_destruct() → sk_prot_free() → tracing path).

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ