Database/Kernel, userspace & hypervisor

QEMU VAPIC hypercall lets a privileged guest write into locked SMRAM and run code in SMM
Impact
The VAPIC setup hypercall does not check that the writable RAM alias it creates stays inside the option ROM window, so a guest with root can point that alias at locked SMRAM. That defeats the chipset D_LCK protection and lets the guest inject code into System Management Mode memory - the most privileged execution context on the machine, below the hypervisor. On a GPU cloud that rents VMs with passthrough accelerators, this is a tenant-to-host trust boundary break: SMM code persists across guest reboots and is invisible to the host kernel, so a compromised node cannot be trusted again by wiping the guest. Red Hat scores it 8.2 with scope change, reflecting the escape out of the VM.
Who can reach it
A privileged (root) user inside a guest on a Q35/KVM machine type. No access to the host or the management network is needed; local guest privilege is enough.
What to do
Apply the QEMU update from your distribution when it ships - Red Hat tracks this for RHEL 6 through 10, RHEL for NVIDIA 26 and OpenShift Container Platform 4, and the upstream fix is tracked in the QEMU project work item. Updating QEMU requires restarting or live-migrating every guest on the host to pick up the new binary, so plan an evacuation pass across the fleet rather than an in-place restart. Until patched, guests whose root is untrusted should not run on hosts you need to keep clean.
References
Related entries
- Linux NFSD: NFSv2 SETATTR/CREATE useconds wrap to a bogus tv_nsec on 32-bit serversCVE-2026-89665 · Linux kernel NFSD (svcxdr_decode_sattr, NFSv2 useconds conversion)High
- Linux NFSD: bogus WARN_ON_ONCE fires on NFS re-export lookupsCVE-2026-89711 · Linux kernel NFSD (nfsd_mode_check WARN_ON_ONCE, NFS re-export)High
- Linux kernel nvme-tcp: a controller can force a host WARN by answering a write with C2HDataCVE-2026-89973 · Linux kernel nvme-tcp (C2HData PDU direction check)High
- Linux iommu/vt-d: probe failure frees a PASID table still referenced by live context entriesCVE-2026-90241 · Linux kernel iommu/vt-d (scalable-mode context teardown on probe failure)High
- Linux kernel NVMe driver (FDP configurations log parsing): While walking the Flexible Data Placement configurationsCVE-2026-97433 · Linux kernel NVMe driver (FDP configurations log parsing)High
- Linux kernel x86/mm/pat: split page tables bypass kernel page table tracking, leaving stale IOTLB entries after freeCVE-2026-97525 · Linux kernel x86 CPA/PAT (__split_large_page kernel page table allocation)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.