VulnerabilityPublished 28 Oct 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99177

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

Data as of 28 Oct 2026, 13:57 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · 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.

ghsa-92wr-6h6p-mvpr

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–

AI-suggested

A fix has been implemented in the Linux kernel to replace set_page_dirty() with set_page_dirty_lock() in sev_gmem_post_populate(). Users should update to the fixed kernel version once available. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's KVM SEV component related to improper page dirtying in the sev_gmem_post_populate() function has been fixed. The issue involved the use of set_page_dirty() without holding the required lock, which could lead to concurrency issues with page mappings. The fix replaces set_page_dirty() with set_page_dirty_lock() to ensure proper locking.

Impact

The vulnerability could lead to race conditions in page dirtying within the KVM SEV subsystem, potentially causing memory corruption or instability in virtualized environments using SEV. However, no known exploits in the wild have been reported, and the impact details are limited to the concurrency issue described.

Summary

The Linux kernel's KVM SEV subsystem had a flaw in the sev_gmem_post_populate() function where set_page_dirty() was called on a page obtained via get_user_pages_fast() without holding the necessary lock. This could cause race conditions because set_page_dirty() expects the caller to hold a lock to prevent the page's mapping from being concurrently removed. The patch replaces this call with set_page_dirty_lock(), which safely marks the page dirty while holding the appropriate lock, resolving the concurrency issue.

References

Community reviews

Loading reviews…