Answer in brief
CVE-2024-57793 records a Unknown severity vulnerability in virt: tdx-guest: Just leak decrypted memory on unrecoverable errors. 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 | >=f4738f56d1dc62aaba69b33702a5ab098f1b8c63 <1429ae7b7d4759a1e362456b8911c701bae655b4 || >=f4738f56d1dc62aaba69b33702a5ab098f1b8c63 <27834971f616c5e154423c578fa95e0444444ce1 | 1429ae7b7d4759a1e362456b8911c701bae655b4, 27834971f616c5e154423c578fa95e0444444ce1 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jan 11, 2025
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: tdx-guest: Just leak decrypted memory on unrecoverable errors In CoCo VMs it is possible for the untrusted host to cause set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. Leak the decrypted memory when set_memory_decrypted() fails, and don't need to print an error since set_memory_decrypted() will call WARN_ONCE().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-57793 records a Unknown severity vulnerability in virt: tdx-guest: Just leak decrypted memory on unrecoverable errors. 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 | >=f4738f56d1dc62aaba69b33702a5ab098f1b8c63 <1429ae7b7d4759a1e362456b8911c701bae655b4 || >=f4738f56d1dc62aaba69b33702a5ab098f1b8c63 <27834971f616c5e154423c578fa95e0444444ce1 | 1429ae7b7d4759a1e362456b8911c701bae655b4, 27834971f616c5e154423c578fa95e0444444ce1 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Jan 11, 2025
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: tdx-guest: Just leak decrypted memory on unrecoverable errors In CoCo VMs it is possible for the untrusted host to cause set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. Leak the decrypted memory when set_memory_decrypted() fails, and don't need to print an error since set_memory_decrypted() will call WARN_ONCE().
Quoted source text, attributed separately from HOL analysis.