Answer in brief
CVE-2026-64104 records a Unknown severity vulnerability in virt: sev-guest: Explicitly leak pages in unknown state. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3e385c0d6ce88ac9916dcf84267bd5855d830748 <bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0 || >=3e385c0d6ce88ac9916dcf84267bd5855d830748 <3d0cd0065deeb054b4b29236432e851806b7cc81 || >=3e385c0d6ce88ac9916dcf84267bd5855d830748 <fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf || 0b16521f95c875e79d657cb8d6911c15080dbb80 || >=6.13.8 <6.14 | bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0, 3d0cd0065deeb054b4b29236432e851806b7cc81, fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64104 records a Unknown severity vulnerability in virt: sev-guest: Explicitly leak pages in unknown state. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3e385c0d6ce88ac9916dcf84267bd5855d830748 <bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0 || >=3e385c0d6ce88ac9916dcf84267bd5855d830748 <3d0cd0065deeb054b4b29236432e851806b7cc81 || >=3e385c0d6ce88ac9916dcf84267bd5855d830748 <fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf || 0b16521f95c875e79d657cb8d6911c15080dbb80 || >=6.13.8 <6.14 | bee400ad4f4259c9c0758e4f1960a1eed6f6f9f0, 3d0cd0065deeb054b4b29236432e851806b7cc81, fd948c3f96b18ff9ba7d3e8eae13d196593e1aaf, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.