Description
In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix invalid wait context in ctx_sched_in() Lockdep found a bug in the event scheduling when a pinned event was failed and wakes up the threads in the ring buffer like below. It seems it should not grab a wait-queue lock under perf-context lock. Let's do it with irq_work. [ 39.913691] ============================= [ 39.914157] [ BUG: Invalid wait context ] [ 39.914623] 6.15.0-next-20250530-next-2025053 #1 Not tainted [ 39.915271] ----------------------------- [ 39.915731] repro/837 is trying to lock: [ 39.916191] ffff88801acfabd8 (&event->waitq){....}-{3:3}, at: __wake_up+0x26/0x60 [ 39.917182] other info that might help us debug this: [ 39.917761] context-{5:5} [ 39.918079] 4 locks held by repro/837: [ 39.918530] #0: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: __perf_event_task_sched_in+0xd1/0xbc0 [ 39.919612] #1: ffff88806ca3c6f8 (&cpuctx_lock){....}-{2:2}, at: __perf_event_task_sched_in+0x1a7/0xbc0 [ 39.920748] #2: ffff88800d91fc18 (&ctx->lock){....}-{2:2}, at: __perf_event_task_sched_in+0x1f9/0xbc0 [ 39.921819] #3: ffffffff8725cd00 (rcu_read_lock){....}-{1:3}, at: perf_event_wakeup+0x6c/0x470
Product status
f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6 (git) before c67ab059953e3b66cb17ddd6524c23f9e1f6526d
f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6 (git) before 825f218ca70ef394c2b8546b313711d867b24584
f4b07fd62d4d11d57a15cb4ae01b3833282eb8f6 (git) before 486ff5ad49bc50315bcaf6d45f04a33ef0a45ced
6.15
Any version before 6.15
6.18.17 (semver)
6.19.7 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/c67ab059953e3b66cb17ddd6524c23f9e1f6526d
git.kernel.org/...c/825f218ca70ef394c2b8546b313711d867b24584
git.kernel.org/...c/486ff5ad49bc50315bcaf6d45f04a33ef0a45ced