perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9bb5d40cd93c9dd4be74834b1dcb1ba03629716b · < da3c256e2d0ebc87c7db0c605c9692b6f1722074| No fix yet |
| Linux Linux |
|
|
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)
From the CVE record · Linux
A race between perf_event_set_output() and perf_mmap_close() can leave a perf event attached to an unmapped ring buffer. A local process using perf event operations can then trigger an infinite loop in a subsequent perf_mmap() call. The input does not specify whether authentication or special privileges are required.
Engineers running the Linux kernel should check whether their kernel includes the perf/core race fix; affected versions are not specified.