GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Check your stack
CVE-2026-99177unknown

KVM: SEV: Fix page dirtying in sev_gmem_post_populate()

Impact

In the Linux kernel, the following vulnerability has been resolved:

Source excerpt · Linux
Applies when

set_page_dirty() requires that the caller holds some kind of lock to ensure that the page's mapping does not concurrently go away.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Linux · Linux

Other versions: unaffected

Version / rangeSource status
97cd21d57e9bd2da79845178d9250cfd19289cd4 to before 184382f9852d433af21de96c334ecf43b8414ed8affected
97cd21d57e9bd2da79845178d9250cfd19289cd4 to before 97818b2fa7082e940ddd36dab12a68615300e798affected
Linux version evidence

Linux · Linux

Other versions: affected

Version / rangeSource status
7.2affected
0 to before 7.2unaffected
7.2.13 through 7.2.* (inclusive)unaffected
7.3 through * (inclusive)unaffected
Linux version evidence

Original source 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