In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When… (CVE-2026-64104)
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When set_memory_{encrypted,decrypted}() fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view of the caller. Since the pages may be left in an unencrypted state, they are not suitable for general use, and cannot be returned safely to the buddy allocator. Avoid the issue by never freeing the pages, and then do the proper accounting by calling snp_leak_pages().
AI Analysis
Technical Summary
The vulnerability in the Linux kernel relates to the handling of memory pages in the SEV-guest feature. When the functions set_memory_encrypted or set_memory_decrypted fail, the caller cannot determine the failure point, resulting in pages left in an unknown encryption state. Because these pages may remain unencrypted, they are unsuitable for reuse and cannot be safely returned to the buddy allocator. The resolution explicitly leaks these pages and performs correct accounting by invoking snp_leak_pages(), preventing unsafe reuse of potentially unencrypted memory.
Potential Impact
Pages left in an unknown encryption state may be unencrypted and thus expose sensitive data if reused improperly. This could lead to information disclosure risks within SEV-guest virtualized environments. However, the vulnerability is addressed by explicitly leaking such pages and accounting for them, preventing unsafe memory reuse.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to explicitly leak pages left in an unknown state and properly account for them using snp_leak_pages(). Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When… (CVE-2026-64104)
Description
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When set_memory_{encrypted,decrypted}() fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view of the caller. Since the pages may be left in an unencrypted state, they are not suitable for general use, and cannot be returned safely to the buddy allocator. Avoid the issue by never freeing the pages, and then do the proper accounting by calling snp_leak_pages().
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel relates to the handling of memory pages in the SEV-guest feature. When the functions set_memory_encrypted or set_memory_decrypted fail, the caller cannot determine the failure point, resulting in pages left in an unknown encryption state. Because these pages may remain unencrypted, they are unsuitable for reuse and cannot be safely returned to the buddy allocator. The resolution explicitly leaks these pages and performs correct accounting by invoking snp_leak_pages(), preventing unsafe reuse of potentially unencrypted memory.
Potential Impact
Pages left in an unknown encryption state may be unencrypted and thus expose sensitive data if reused improperly. This could lead to information disclosure risks within SEV-guest virtualized environments. However, the vulnerability is addressed by explicitly leaking such pages and accounting for them, preventing unsafe memory reuse.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to explicitly leak pages left in an unknown state and properly account for them using snp_leak_pages(). Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8rjp-wmfg-59v9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64104"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912b8a3
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:48:59 UTC
Last updated: 07/20/2026, 19:41:21 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.