First published: Tue Aug 23 2022(Updated: )
A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tulip reads or writes to the rx/tx descriptor or copies the rx/tx frame, it doesn't check whether the destination address is its own MMIO address. This can cause the device to trigger MMIO handlers multiple times, possibly leading to a stack or heap overflow. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/qemu | <7.2.0 | 7.2.0 |
QEMU KVM | >=4.2.0<=7.1.0 | |
debian/qemu | 1:5.2+dfsg-11+deb11u3 1:5.2+dfsg-11+deb11u2 1:7.2+dfsg-7+deb12u12 1:9.2.0+ds-5 1:9.2.1+ds-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2022-2962.
The severity of CVE-2022-2962 is high with a CVSS score of 7.8.
The affected software includes QEMU versions 1:7.0+dfsg-7ubuntu2.1, 7.2.0, and versions between 4.2.0 and 7.1.0, as well as various Debian versions.
The vulnerability in Tulip device emulation in QEMU allows the device to trigger MMIO handlers multiple times, potentially leading to arbitrary code execution or denial of service.
Yes, you can find more information about CVE-2022-2962 at the following references: [Link 1](https://gitlab.com/qemu-project/qemu/-/commit/36a894aeb64a2e02871016da1c37d4a4ca109182), [Link 2](https://gitlab.com/qemu-project/qemu/-/issues/1171), [Link 3](https://launchpad.net/bugs/cve/CVE-2022-2962).