A flaw was found in QEMU. The VAPIC setup hypercall in hw/i386/vapic.c does not validate that the writable RAM alias remains within the option ROM window. A privileged guest user on a Q35/KVM machine can position this alias over locked SMRAM, bypassing chipset D_LCK protection and injecting code into System Management Mode memory.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade qemu-system-x86Upgrade qemu-testsUpgrade qemu-docsUpgrade qemu-pr-helperUpgrade qemu-user-static-aarch64-debuginfoUpgrade qemu-system-x86-core-debuginfoUpgrade qemu-tests-debuginfoUpgrade qemu-user-static-x86Upgrade qemu-pr-helper-debuginfoUpgrade qemu-kvm-coreUpgrade qemu-system-aarch64-coreUpgrade qemu-imgUpgrade qemu-guest-agentUpgrade qemu-user-static-aarch64Upgrade qemu-user-static-x86-debuginfoUpgrade qemu-tools-debuginfoUpgrade qemu-userUpgrade qemu-system-aarch64-core-debuginfoUpgrade qemu-system-x86-coreUpgrade qemu-user-debuginfoUpgrade qemu-toolsUpgrade qemuUpgrade qemu-img-debuginfoUpgrade qemu-user-binfmtUpgrade qemu-system-aarch64Upgrade qemu-common-debuginfoUpgrade qemu-user-staticUpgrade qemu-kvmUpgrade qemu-guest-agent-debuginfoUpgrade qemu-debuginfoUpgrade qemu-commonUpgrade qemu-debugsource | Oct 28, 2026 | Sep 18, 2026 |
| Redhat_linux | — | No solution exists | Sep 21, 2026 | Aug 26, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub