Linux KVM SEV: sub-page command buffer on SNP hosts triggers RMP faults and host panic

Impact

When KVM {de,en}crypts memory of an SEV or SEV-ES guest on an SNP-enabled host, it used a sub-page temporary buffer, so the page handed to AMD firmware also held unrelated kernel allocations. Transferring a page to Firmware ownership makes it inaccessible to software, so any other kernel code touching the rest of that page takes an RMP violation #PF - the bug report shows a panic arriving through an unrelated getxattr path. The result is a full host panic on a confidential-computing hypervisor: every guest on the box dies at once, and on a GPU host that is every tenant sharing those GPUs plus a cold reboot rather than a drain. This is a host stability failure driven by normal SEV guest lifecycle operations, not an escape.

Who can reach it

Local. Triggered by KVM servicing SEV/SEV-ES memory encrypt/decrypt commands on an SNP-enabled AMD host; a tenant able to run or manipulate an SEV guest can drive the code path, but the fault lands on whichever kernel allocation happens to share the page, so timing decides whether it panics. No remote or unauthenticated path.

What to do

Apply the stable kernel fix (linked commits) and reboot each affected hypervisor node - this is a kernel change, so drain the node and reboot; there is no runtime toggle. The record names no fixed release version, only the commits. Short of patching, the only avoidance is not running SEV/SEV-ES guests on SNP-enabled hosts.

References

Related entries

• Linux kernel FUSE: interrupted DAX truncate on O_TRUNC open leaks the invalidate lock, wedging the fileCVE-2026-80855 · Linux kernel FUSE (DAX truncate path in fuse_open)Unscored
• Linux kernel FUSE: setattr writeback failure leaks the invalidate lock on a DAX truncateCVE-2026-80856 · Linux kernel FUSE (DAX truncate path in fuse_do_setattr)Unscored
• Linux kernel FUSE: abort_on_kill returns without waiting for FR_FINISHED, freeing an in-flight requestCVE-2026-80857 · Linux kernel FUSE request handling (request_wait_answer abort_on_kill path)Unscored
• Linux kernel FUSE: io_uring queues published without release ordering can be read half-initializedCVE-2026-80858 · Linux kernel FUSE (io_uring queue publication ordering)Unscored
• Linux kernel FUSE: missing read barrier in the io-uring readiness check can reintroduce a lock-order deadlockCVE-2026-80859 · Linux kernel FUSE (fuse-over-io-uring readiness check in fuse_block_alloc)Unscored
• Linux kernel FUSE: race between request interrupt and resend leaves a request queued on the interrupt listCVE-2026-80860 · Linux kernel FUSE (interrupt vs. resend request handling)Unscored