[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAP=Rh=Oo1KdREOq8=B6wCBOcQ6H=uwELS8MFaMtvr-a28LAxGA@mail.gmail.com>
Date: Wed, 21 May 2025 21:39:06 +0800
From: John <john.cs.hey@...il.com>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Will Deacon <will@...nel.org>, Boqun Feng <boqun.feng@...il.com>
Cc: Waiman Long <longman@...hat.com>, linux-kernel@...r.kernel.org
Subject: [Bug] "BUG: soft lockup in ip_list_rcv" 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: __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152
Bug report: https://pastebin.com/t6jtEzp1
Complete log: https://pastebin.com/g096W4xD
Entire kernel config: https://pastebin.com/MRWGr3nv
Root Cause Analysis:
A soft lockup occurred on CPU#0 for 22 seconds during execution of
avc_alloc_node() inside an IRQ context. The lockup is rooted in
spinlock contention within SELinux AVC (Access Vector Cache) node
allocation,
possibly triggered by a storm of SELinux permission checks
(avc_has_perm() calls), while audit is in permissive=1 mode, leading
to continuous allocation and reclamation of avc_node objects.
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