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.
CVE-2022-35414
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-07-12. NVD baseline CVSS 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 49%
- KEV
- Not listed
Published
July 11, 2022
Last Modified
November 21, 2024
Advisory Details (10)
Auto-updated Aug 5, 2026Security — QEMU documentation
https://www.qemu.org/docs/master/system/security.html#non-virtualization-use-caseRe: [PATCH v2] softmmu: Always initialize xlat in address_space_translate_for_iotlb
https://www.mail-archive.com/qemu-devel%40nongnu.org/msg895266.htmlCVE-2022-35414 - QEMU 4.1.50 through QEMU 7.0.0 - address_space_translate_for_iotlb allows a guest user to crash a host resulting in a denial of service. - Sick Codes - Security Research, Hardware & Software Hacking, Consulting, Linux, IoT, Cloud, Embedded, Arch, Tweaks & Tips!
https://sick.codes/sick-2022-113[SECURITY] [DLA 3099-1] qemu security update
https://lists.debian.org/debian-lts-announce/2022/09/msg00008.htmlcputlb: uninitialized local variable in tlb_set_page_with_attrs cause SIGSEGV when a CPU access an unmapped IOMMU page (#1065) · Issues · QEMU / QEMU · GitLab
https://gitlab.com/qemu-project/qemu/-/issues/1065commit 418ade7849ce (qemu/qemu)
Fix landed in qemu/qemu commit 418ade7849ce — awaiting tagged release
https://github.com/qemu/qemu/commit/418ade7849ce7641c0f7333718caf5091a02fd4ccommit 3517fb726741 (qemu/qemu)
Fix landed in qemu/qemu commit 3517fb726741 — awaiting tagged release
https://github.com/qemu/qemu/commit/3517fb726741c109cae7995f9ea46f0cab6187d6#diff-83c563ed6330dc5d49876f1116e7518b5c16654bbc6e9b4ea8e28f5833d576fcR482.aacommit 3517fb726741 (qemu/qemu)
Fix landed in qemu/qemu commit 3517fb726741 — awaiting tagged release
https://github.com/qemu/qemu/commit/3517fb726741c109cae7995f9ea46f0cab6187d6#diff-83c563ed6330dc5d49876f1116e7518b5c16654bbc6e9b4ea8e28f5833d576fcR482qemu/include/exec/cpu-all.h at v7.0.0 · qemu/qemu · GitHub
https://github.com/qemu/qemu/blob/v7.0.0/include/exec/cpu-all.h#L145-L148qemu/softmmu/physmem.c at f200ff158d5abcb974a6b597a962b6b2fbea2b06 · qemu/qemu · GitHub
https://github.com/qemu/qemu/blob/f200ff158d5abcb974a6b597a962b6b2fbea2b06/softmmu/physmem.cVendor Advisories for CVE-2022-35414(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(5 across 5 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| qemu | 1:3.1+dfsg-8 ... 1:3.1+dfsg-8~deb10u1 (9 versions) | 1:3.1+dfsg-8+deb10u9 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| qemu | 1:10.0.0+ds-1 ... 1:9.2.2+ds-1~bpo12+1 (225 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| qemu | — | 1:7.1+dfsg-1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| qemu | — | 1:7.1+dfsg-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| qemu | — | 1:7.1+dfsg-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 31× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 163 total refreshes for this CVE.
- 2026-09-07 15:58 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 09:48 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 01:19 UTCEPSS rescore
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-27 14:22 UTCEPSS rescore
- 2026-08-26 14:43 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-24 14:13 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-19 17:01 UTCEPSS rescore
- 2026-08-18 20:10 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescore
- 2026-08-17 13:44 UTCEPSS rescore
- 2026-08-16 14:53 UTCEPSS rescore
- 2026-08-16 02:11 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-15 01:27 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-11 13:39 UTCEPSS rescore
- 2026-08-10 14:08 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:34 UTCEPSS rescore
- 2026-08-07 16:24 UTCEPSS rescore
- 2026-08-06 13:44 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-04 10:35 UTCEPSS rescore
- 2026-08-03 16:27 UTCOSV refresh
- 2026-08-02 02:24 UTCEPSS rescore
- 2026-08-01 04:13 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:33 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:12 UTCEG score recompute
- 2026-07-22 22:59 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-17 03:24 UTCOSV refresh
- 2026-07-16 17:00 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
- 2026-07-08 15:12 UTCEPSS rescore
- 2026-07-07 13:44 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 02:21 UTCEPSS rescore
- 2026-07-06 02:21 UTCEPSS rescore
- 2026-07-05 02:28 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-01 15:04 UTCEPSS rescore
- 2026-06-30 23:20 UTCEPSS rescore
- 2026-06-30 23:20 UTCEPSS rescore
- 2026-06-29 14:04 UTCEPSS rescore
- 2026-06-29 01:32 UTCOSV refresh
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 04:54 UTCEPSS rescore
- 2026-06-28 04:54 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-24 14:03 UTCEPSS rescore
Frequently asked(5)
What is CVE-2022-35414?
When was CVE-2022-35414 disclosed?
Is CVE-2022-35414 actively exploited?
What is the CVSS score of CVE-2022-35414?
How do I remediate CVE-2022-35414?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-35414
Is Your Infrastructure Affected by CVE-2022-35414?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.