CVE-2022-49607

published 26 Feb 2025 · updated 17 Nov 2026

perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()

4.7MediumCVSS 4.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f836f9ac95df15f1e0af4beb0ec20021e8c91998, Kernel 3.3, Kernel 3.5 and 15 more.

In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() Yang Jihing reported a race between perf_event_set_output() and perf_mmap_close(): CPU1 CPU2 perf_mmap_close(e2) if (atomic_dec_and_test(&e2->rb->mmap_count)) // 1 - > 0 detach_rest = true ioctl(e1, IOC_SET_OUTPUT, e2) perf_event_set_output(e1, e2) ... list_for_each_entry_rcu(e, &e2->rb->event_list, rb_entry) ring_buffer_attach(e, NULL); // e1 isn't yet added and // therefore not detached ring_buffer_attach(e1, e2->rb) list_add_rcu(&e1->rb_entry, &e2->rb->event_list) After this; e1 is attached to an unmapped rb and a subsequent perf_mmap() will loop forever more: again: mutex_lock(&e->mmap_mutex); if (event->rb) { ... if (!atomic_inc_not_zero(&e->rb->mmap_count)) { ... mutex_unlock(&e->mmap_mutex); goto again; } } The loop in perf_mmap_close() holds e2->mmap_mutex, while the attach in perf_event_set_output() holds e1->mmap_mutex. As such there is no serialization to avoid this race. Change perf_event_set_output() to take both e1->mmap_mutex and e2->mmap_mutex to alleviate that problem. Additionally, have the loop in perf_mmap() detach the rb directly, this avoids having to wait for the concurrent perf_mmap_close() to get around to doing it to make progress.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <f836f9ac95df15f1e0af4beb0ec20021e8c91998, >=3.2.49 <3.3, >=3.4.52 <3.5, >=3.9.8 <3.10, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <17f5417194136517ee9bbd6511249e5310e5617c, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <3bbd868099287ff9027db59029b502fcfa2202a0, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <43128b3eee337824158f34da6648163d2f2fb937, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <68e3c69803dada336893640110cb87221bb01dcf, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <98c3c8fd0d4c560e0f8335b79c407bbf7fc9462c, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <a9391ff7a7c5f113d6f2bf6621d49110950de49c, >=9bb5d40cd93c9dd4be74834b1dcb1ba03629716b <da3c256e2d0ebc87c7db0c605c9692b6f1722074, =2487f0db30527032c4d56fc2d0b1a240fe89fef8, =3.10, =703197b61d05f5edae54bad3256901c5a5c8794c, =c52217e88ae0f3a4ae00562d86e338f8f85969b4f836f9ac95df15f1e0af4beb0ec20021e8c91998, 3.3, 3.5, 3.10, 17f5417194136517ee9bbd6511249e5310e5617c, 3bbd868099287ff9027db59029b502fcfa2202a0, 43128b3eee337824158f34da6648163d2f2fb937, 68e3c69803dada336893640110cb87221bb01dcf, 98c3c8fd0d4c560e0f8335b79c407bbf7fc9462c, a9391ff7a7c5f113d6f2bf6621d49110950de49c, da3c256e2d0ebc87c7db0c605c9692b6f1722074
linux-kernel: Kernel>=3.2.49 <3.3, >=3.4.52 <3.5, >=3.9.8 <3.10, >=4.10.0 <4.14.290, >=4.15.0 <4.19.254, >=4.20.0 <5.4.208, >=5.11.0 <5.15.58, >=5.16.0 <5.18.15, >=5.5.0 <5.10.134, >=3.10.0 <4.9.3253.3, 3.5, 3.10, 4.14.290, 4.19.254, 5.4.208, 5.15.58, 5.18.15, 5.10.134, 4.9.325

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-49607 severity on Zeptric[![CVE-2022-49607](https://zeptric.io/badge/cve/CVE-2022-49607.svg)](https://zeptric.io/cve/CVE-2022-49607)