| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37884: bpf: Fix deadlock between rcu_tasks_trace and event_mutex. |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| bpf: Fix deadlock between rcu_tasks_trace and event_mutex. |
| |
| Fix the following deadlock: |
| CPU A |
| _free_event() |
| perf_kprobe_destroy() |
| mutex_lock(&event_mutex) |
| perf_trace_event_unreg() |
| synchronize_rcu_tasks_trace() |
| |
| There are several paths where _free_event() grabs event_mutex |
| and calls sync_rcu_tasks_trace. Above is one such case. |
| |
| CPU B |
| bpf_prog_test_run_syscall() |
| rcu_read_lock_trace() |
| bpf_prog_run_pin_on_cpu() |
| bpf_prog_load() |
| bpf_tracing_func_proto() |
| trace_set_clr_event() |
| mutex_lock(&event_mutex) |
| |
| Delegate trace_set_clr_event() to workqueue to avoid |
| such lock dependency. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37884 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 6.1.136 with commit 255cbc9db7067a83713fd2f4b31034ddd266549a |
| Fixed in 6.6.89 with commit b5a528a34e1f613565115a7a6016862ccbfcb9ac |
| Fixed in 6.12.26 with commit c5c833f6375f8ecf9254dd27946c927c7d645421 |
| Fixed in 6.14.5 with commit 45286680b385f2592db3003554872388dee66d68 |
| Fixed in 6.15 with commit 4580f4e0ebdf8dc8d506ae926b88510395a0c1d1 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-37884 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| kernel/trace/bpf_trace.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/255cbc9db7067a83713fd2f4b31034ddd266549a |
| https://git.kernel.org/stable/c/b5a528a34e1f613565115a7a6016862ccbfcb9ac |
| https://git.kernel.org/stable/c/c5c833f6375f8ecf9254dd27946c927c7d645421 |
| https://git.kernel.org/stable/c/45286680b385f2592db3003554872388dee66d68 |
| https://git.kernel.org/stable/c/4580f4e0ebdf8dc8d506ae926b88510395a0c1d1 |
