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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 8.2 · red hatNVD modified 2026-10-30 20:05
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 3
- https://access.redhat.com/security/cve/CVE-2026-81627 vdb-entry, x_refsource_redhat
- https://bugzilla.redhat.com/show_bug.cgi?id=2536950 issue-tracking, x_refsource_redhat
- https://gitlab.com/qemu-project/qemu/-/work_items/4206