[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024022952-CVE-2021-47061-6fea@gregkh>
Date: Thu, 29 Feb 2024 23:37:58 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2021-47061: KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
KVM: Destroy I/O bus devices on unregister failure _after_ sync'ing SRCU
If allocating a new instance of an I/O bus fails when unregistering a
device, wait to destroy the device until after all readers are guaranteed
to see the new null bus. Destroying devices before the bus is nullified
could lead to use-after-free since readers expect the devices on their
reference of the bus to remain valid.
The Linux kernel CVE team has assigned CVE-2021-47061 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.9 with commit f65886606c2d and fixed in 5.10.37 with commit 03c6cccedd39
Issue introduced in 5.9 with commit f65886606c2d and fixed in 5.11.21 with commit 4e899ca84863
Issue introduced in 5.9 with commit f65886606c2d and fixed in 5.12.4 with commit 30f46c699373
Issue introduced in 5.9 with commit f65886606c2d and fixed in 5.13 with commit 2ee3757424be
Please see https://www.kernel.org or 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-2021-47061
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:
virt/kvm/kvm_main.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/03c6cccedd3913006744faa252a4da5145299343
https://git.kernel.org/stable/c/4e899ca848636b37e9ac124bc1723862a7d7d927
https://git.kernel.org/stable/c/30f46c6993731efb2a690c9197c0fd9ed425da2d
https://git.kernel.org/stable/c/2ee3757424be7c1cd1d0bbfa6db29a7edd82a250
Powered by blists - more mailing lists