VulnerabilityPublished 28 Oct 2026

CVE-2026-99177: Linux kernel · KVM: SEV: Fix page dirtying in sev_gmem_post_populate()

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to 184382f9852d433af21de96c334ecf43b8414ed8 or 97818b2fa7082e940ddd36dab12a68615300e798 when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 184382f9852d433af21de96c334ecf43b8414ed8, 97818b2fa7082e940ddd36dab12a68615300e798

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 184382f9852d433af21de96c334ecf43b8414ed8 or 97818b2fa7082e940ddd36dab12a68615300e798.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 97cd21d57e9bd2da79845178d9250cfd19289cd4, < 184382f9852d433af21de96c334ecf43b8414ed8	Fixed in 184382f9852d433af21de96c334ecf43b8414ed8
LinuxLinux	Affected ≥ 97cd21d57e9bd2da79845178d9250cfd19289cd4, < 97818b2fa7082e940ddd36dab12a68615300e798	Fixed in 97818b2fa7082e940ddd36dab12a68615300e798
LinuxLinux	Affected =7.2	Fixed in–

Description

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]

References

Community reviews

Loading reviews…