Live › vulnerability › CVE-2026-99177
Go to dashboardIn the Linux kernel's KVM SEV code, a page is marked dirty without holding the lock that keeps its mapping from disappearing, which can corrupt memory state. The sources do not say what an attacker can gain from it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
Only hosts running the Linux kernel KVM module with AMD SEV guests, using guest memory from userspace, are in scope. Hosts without AMD SEV-enabled KVM guests can likely skip it, but the sources do not confirm this.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel builds listed in the NVD entryls /dev/sev on AMD EPYC hosts running KVMEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
KVM: SEV: Fix page dirtying in sev_gmem_post_populate()
set_page_dirty() requires that the caller holds some kind of lock to ensure that the page's mapping does not concurrently go away. That is not the case for a random page we got from get_user_pages_fast(), so use set_page_dirty_lock().
[sean: tag for stable]
This page as .md · .json · in your agent: get_signal("CVE-2026-99177")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.