CVE-2022-35414
published 2022-07-11CVE-2022-35414: softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. NOTE: a third…
PriorityP341high8.8CVSS 3.1
AVLACLPRLUINSCCHIHAH
EPSS
0.66%
47.4th percentile
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization Use Case in the qemu.org reference applies here, i.e., "Bugs affecting the non-virtualization use case are not considered security bugs at this time.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | qemu | < qemu 1:7.1+dfsg-1 (bookworm) | qemu 1:7.1+dfsg-1 (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-7_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-43_on_cbl_mariner_1.0 | — | — |
| qemu | qemu | >= 0 < 1:7.1+dfsg-1 | 1:7.1+dfsg-1 |
| qemu | qemu | >= 0 < 1:7.1+dfsg-1 | 1:7.1+dfsg-1 |
| qemu | qemu | >= 0 < 1:7.1+dfsg-1 | 1:7.1+dfsg-1 |
| qemu | qemu | 4.1.50 – 7.0.0 | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvdv2.06.1MEDIUMAV:L/AC:L/Au:N/C:P/I:P/A:C
osv8.8HIGH
vendor_debian8.8LOW
vendor_msrc8.8HIGH
vendor_redhat8.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.
GHSA
GHSA-78j4-r4gh-xcm9: softmmu/physmem
ghsa_unreviewed·2022-07-12
CVE-2022-35414 [HIGH] CWE-908 GHSA-78j4-r4gh-xcm9: softmmu/physmem
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash.
OSV
CVE-2022-35414: softmmu/physmem
osv·2022-07-11·CVSS 8.8
CVE-2022-35414 [HIGH] CVE-2022-35414: softmmu/physmem
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization Use Case in the qemu.org reference applies here, i.e., "Bugs affecting the non-virtualization use case are not considered security bugs at this time.
Microsoft
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization U
vendor_msrc·2022-07-12·CVSS 8.8
CVE-2022-35414 [HIGH] CWE-908 softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization U
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization Use Case in the qemu.org reference applies here i.e. "Bugs affecting the non-virtualization use case are not considered security bugs at this time.
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 with which the distro is composed. Microsoft is committed to transparency in this work which is why we bega
Red Hat
QEMU: cputlb: uninitialized read during address translation leads to a crash
vendor_redhat·2022-07-11·CVSS 8.8
CVE-2022-35414 [HIGH] CWE-457 QEMU: cputlb: uninitialized read during address translation leads to a crash
QEMU: cputlb: uninitialized read during address translation leads to a crash
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization Use Case in the qemu.org reference applies here, i.e., "Bugs affecting the non-virtualization use case are not considered security bugs at this time.
Statement: According to https://www.qemu.org/docs/master/system/security.html#non-virtualization-use-case, bugs affecting the Tiny Code Generator (TCG) are not considered security bugs at this time. As a result, Red Hat Product Security does not consider this bug to be a security issue.
Package: qemu-kvm (Red Hat Enterprise Linux 6) - Not affected
Package: qemu-kvm (
Debian
CVE-2022-35414: qemu - softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the...
vendor_debian·2022·CVSS 8.8
CVE-2022-35414 [HIGH] CVE-2022-35414: qemu - softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the...
softmmu/physmem.c in QEMU through 7.0.0 can perform an uninitialized read on the translate_fail path, leading to an io_readx or io_writex crash. NOTE: a third party states that the Non-virtualization Use Case in the qemu.org reference applies here, i.e., "Bugs affecting the non-virtualization use case are not considered security bugs at this time.
Scope: local
bookworm: resolved (fixed in 1:7.1+dfsg-1)
bullseye: open
forky: resolved (fixed in 1:7.1+dfsg-1)
sid: resolved (fixed in 1:7.1+dfsg-1)
trixie: resolved (fixed in 1:7.1+dfsg-1)
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/qemu/qemu/blob/f200ff158d5abcb974a6b597a962b6b2fbea2b06/softmmu/physmem.chttps://github.com/qemu/qemu/blob/v7.0.0/include/exec/cpu-all.h#L145-L148https://github.com/qemu/qemu/commit/3517fb726741c109cae7995f9ea46f0cab6187d6#diff-83c563ed6330dc5d49876f1116e7518b5c16654bbc6e9b4ea8e28f5833d576fcR482https://github.com/qemu/qemu/commit/3517fb726741c109cae7995f9ea46f0cab6187d6#diff-83c563ed6330dc5d49876f1116e7518b5c16654bbc6e9b4ea8e28f5833d576fcR482.aahttps://github.com/qemu/qemu/commit/418ade7849ce7641c0f7333718caf5091a02fd4chttps://gitlab.com/qemu-project/qemu/-/issues/1065https://lists.debian.org/debian-lts-announce/2022/09/msg00008.htmlhttps://sick.codes/sick-2022-113https://www.mail-archive.com/qemu-devel%40nongnu.org/msg895266.htmlhttps://www.qemu.org/docs/master/system/security.html#non-virtualization-use-casehttps://github.com/qemu/qemu/blob/f200ff158d5abcb974a6b597a962b6b2fbea2b06/softmmu/physmem.chttps://github.com/qemu/qemu/blob/v7.0.0/include/exec/cpu-all.h#L145-L148https://github.com/qemu/qemu/commit/3517fb726741c109cae7995f9ea46f0cab6187d6#diff-83c563ed6330dc5d49876f1116e7518b5c16654bbc6e9b4ea8e28f5833d576fcR482https://github.com/qemu/qemu/commit/3517fb726741c109cae7995f9ea46f0cab6187d6#diff-83c563ed6330dc5d49876f1116e7518b5c16654bbc6e9b4ea8e28f5833d576fcR482.aahttps://github.com/qemu/qemu/commit/418ade7849ce7641c0f7333718caf5091a02fd4chttps://gitlab.com/qemu-project/qemu/-/issues/1065https://lists.debian.org/debian-lts-announce/2022/09/msg00008.htmlhttps://sick.codes/sick-2022-113https://www.mail-archive.com/qemu-devel%40nongnu.org/msg895266.htmlhttps://www.qemu.org/docs/master/system/security.html#non-virtualization-use-case
2022-07-11
Published