CVE-2022-49607

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 isnt 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.

Weakness

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Affected Software

Extended Description

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:

A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Potential Mitigations

• Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
• Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/29.html

References

• https://git.kernel.org/stable/c/17f5417194136517ee9bbd6511249e5310e5617c
• https://git.kernel.org/stable/c/3bbd868099287ff9027db59029b502fcfa2202a0
• https://git.kernel.org/stable/c/43128b3eee337824158f34da6648163d2f2fb937
• https://git.kernel.org/stable/c/68e3c69803dada336893640110cb87221bb01dcf
• https://git.kernel.org/stable/c/98c3c8fd0d4c560e0f8335b79c407bbf7fc9462c
• https://git.kernel.org/stable/c/a9391ff7a7c5f113d6f2bf6621d49110950de49c
• https://git.kernel.org/stable/c/da3c256e2d0ebc87c7db0c605c9692b6f1722074
• https://git.kernel.org/stable/c/f836f9ac95df15f1e0af4beb0ec20021e8c91998