{"uuid": "c2af9a8c-60a0-49e0-9189-ab7ff23df327", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37884", "type": "seen", "source": "https://t.me/cvedetector/24933", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37884 - Linux Kernel BPF Event Mutex Deadlock\", \n  \"Content\": \"CVE ID : CVE-2025-37884 \nPublished : May 9, 2025, 7:16 a.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Fix deadlock between rcu_tasks_trace and event_mutex.  \n  \nFix the following deadlock:  \nCPU A  \n_free_event()  \n  perf_kprobe_destroy()  \n    mutex_lock(&event_mutex)  \n      perf_trace_event_unreg()  \n        synchronize_rcu_tasks_trace()  \n  \nThere are several paths where _free_event() grabs event_mutex  \nand calls sync_rcu_tasks_trace. Above is one such case.  \n  \nCPU B  \nbpf_prog_test_run_syscall()  \n  rcu_read_lock_trace()  \n    bpf_prog_run_pin_on_cpu()  \n      bpf_prog_load()  \n        bpf_tracing_func_proto()  \n          trace_set_clr_event()  \n            mutex_lock(&event_mutex)  \n  \nDelegate trace_set_clr_event() to workqueue to avoid  \nsuch lock dependency. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-09T10:22:00.000000Z"}