CVE-2022-2962
published 2022-09-13CVE-2022-2962: 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…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.38%
30.6th percentile
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.
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | qemu | < qemu 1:7.1+dfsg-2 (bookworm) | qemu 1:7.1+dfsg-2 (bookworm) |
| msrc | azl3_qemu_6.2.0-18_on_azure_linux_3.0 | — | — |
| msrc | azure_linux_3.0_arm | — | — |
| msrc | azure_linux_3.0_x64 | — | — |
| msrc | cbl2_qemu_6.2.0-13_on_cbl_mariner_2.0 | — | — |
| msrc | cbl_mariner_1.0_arm | — | — |
| msrc | cbl_mariner_1.0_x64 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
| msrc | cbl_mariner_2.0_x64 | — | — |
| msrc | cm1_qemu-kvm_4.2.0-48_on_cbl_mariner_1.0 | — | — |
| qemu | qemu | — | — |
| qemu | qemu | >= 0 < 1:7.1+dfsg-2 | 1:7.1+dfsg-2 |
| qemu | qemu | >= 0 < 1:7.1+dfsg-2 | 1:7.1+dfsg-2 |
| qemu | qemu | >= 0 < 1:7.1+dfsg-2 | 1:7.1+dfsg-2 |
| qemu | qemu | >= 0 < 1:2.11+dfsg-1ubuntu7.41 | 1:2.11+dfsg-1ubuntu7.41 |
| qemu | qemu | >= 0 < 1:4.2-3ubuntu6.24 | 1:4.2-3ubuntu6.24 |
| qemu | qemu | >= 0 < 1:6.2+dfsg-2ubuntu6.6 | 1:6.2+dfsg-2ubuntu6.6 |
| qemu | qemu | >= 0 < 2.0.0+dfsg-2ubuntu1.47+esm2 | 2.0.0+dfsg-2ubuntu1.47+esm2 |
| qemu | qemu | >= 0 < 1:2.5+dfsg-5ubuntu10.51+esm1 | 1:2.5+dfsg-5ubuntu10.51+esm1 |
| qemu | qemu | 4.2.0 – 7.1.0 | — |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv8.5HIGH
vendor_ubuntu8.5HIGH
vendor_debian7.8HIGH
vendor_msrc7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2022-12-12·CVSS 8.5
CVE-2021-3682 [HIGH] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
It was discovered that QEMU incorrectly handled bulk transfers from SPICE
clients. A remote attacker could use this issue to cause QEMU to crash,
resulting in a denial of service, or possibly execute arbitrary code. This
issue only affected Ubuntu 14.04 ESM and Ubuntu 16.04 ESM. (CVE-2021-3682)
It was discovered that QEMU did not properly manage memory when it
transfers the USB packets. A malicious guest attacker could use this issue
to cause QEMU to crash, resulting in a denial of service, or possibly
execute arbitrary code. This issue only affected Ubuntu 18.04 LTS, Ubuntu
20.04 LTS and Ubuntu 22.04 LTS. (CVE-2021-3750)
It was discovered that the QEMU SCSI device emulation incorrectly handled
certain MOD
Microsoft
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
vendor_msrc·2022-09-13·CVSS 7.8
CVE-2022-2962 [HIGH] CWE-662 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
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.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries
Red Hat
QEMU: tulip: DMA reentrancy issue leads to stack or heap overflow
vendor_redhat·2022-08-23·CVSS 7.8
CVE-2022-2962 [HIGH] CWE-662 QEMU: tulip: DMA reentrancy issue leads to stack or heap overflow
QEMU: tulip: DMA reentrancy issue leads to stack or heap overflow
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.
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 MMIO address. This issue can cause the device to trigger MMIO handle
Debian
CVE-2022-2962: qemu - A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tul...
vendor_debian·2022·CVSS 7.8
CVE-2022-2962 [HIGH] CVE-2022-2962: qemu - A DMA reentrancy issue was found in the Tulip device emulation in QEMU. When Tul...
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.
Scope: local
bookworm: resolved (fixed in 1:7.1+dfsg-2)
bullseye: resolved
forky: resolved (fixed in 1:7.1+dfsg-2)
sid: resolved (fixed in 1:7.1+dfsg-2)
trixie: resolved (fixed in 1:7.1+dfsg-2)
OSV
qemu vulnerabilities
osv·2022-12-12·CVSS 8.5
CVE-2021-3682 [HIGH] qemu vulnerabilities
qemu vulnerabilities
It was discovered that QEMU incorrectly handled bulk transfers from SPICE
clients. A remote attacker could use this issue to cause QEMU to crash,
resulting in a denial of service, or possibly execute arbitrary code. This
issue only affected Ubuntu 14.04 ESM and Ubuntu 16.04 ESM. (CVE-2021-3682)
It was discovered that QEMU did not properly manage memory when it
transfers the USB packets. A malicious guest attacker could use this issue
to cause QEMU to crash, resulting in a denial of service, or possibly
execute arbitrary code. This issue only affected Ubuntu 18.04 LTS, Ubuntu
20.04 LTS and Ubuntu 22.04 LTS. (CVE-2021-3750)
It was discovered that the QEMU SCSI device emulation incorrectly handled
certain MODE SELECT commands. An attacker inside the guest could possibl
GHSA
GHSA-wmwv-5vwp-c54w: A DMA reentrancy issue was found in the Tulip device emulation in QEMU
ghsa_unreviewed·2022-09-14
CVE-2022-2962 [HIGH] CWE-400 GHSA-wmwv-5vwp-c54w: A DMA reentrancy issue was found in the Tulip device emulation in QEMU
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.
OSV
CVE-2022-2962: A DMA reentrancy issue was found in the Tulip device emulation in QEMU
osv·2022-09-13·CVSS 7.8
CVE-2022-2962 [HIGH] CVE-2022-2962: A DMA reentrancy issue was found in the Tulip device emulation in QEMU
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2022-09-13
Published