Answer in brief
CVE-2024-47727 records a Unknown severity vulnerability in x86/tdx: Fix "in-kernel MMIO" check. 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 | >=31d58c4e557d46fa7f8557714250fb6f89c941ae <25703a3c980e21548774eea8c8a87a75c5c8f58c || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <18ecd5b74682839e7cdafb7cd1ec106df7baa18c || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <bca2e29f7e26ce7c3522f8b324c0bd85612f68e3 || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <d4fc4d01471528da8a9797a065982e05090e1d81 | 25703a3c980e21548774eea8c8a87a75c5c8f58c, 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee, 18ecd5b74682839e7cdafb7cd1ec106df7baa18c, bca2e29f7e26ce7c3522f8b324c0bd85612f68e3, d4fc4d01471528da8a9797a065982e05090e1d81 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Oct 21, 2024
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: x86/tdx: Fix "in-kernel MMIO" check TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not. However, userspace can deceive the kernel into performing MMIO on its behalf. For example, if userspace can point a syscall to an MMIO address, syscall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO. Ensure that the target MMIO address is within the kernel before decoding instruction.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-47727 records a Unknown severity vulnerability in x86/tdx: Fix "in-kernel MMIO" check. 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 | >=31d58c4e557d46fa7f8557714250fb6f89c941ae <25703a3c980e21548774eea8c8a87a75c5c8f58c || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <18ecd5b74682839e7cdafb7cd1ec106df7baa18c || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <bca2e29f7e26ce7c3522f8b324c0bd85612f68e3 || >=31d58c4e557d46fa7f8557714250fb6f89c941ae <d4fc4d01471528da8a9797a065982e05090e1d81 | 25703a3c980e21548774eea8c8a87a75c5c8f58c, 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee, 18ecd5b74682839e7cdafb7cd1ec106df7baa18c, bca2e29f7e26ce7c3522f8b324c0bd85612f68e3, d4fc4d01471528da8a9797a065982e05090e1d81 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Oct 21, 2024
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: x86/tdx: Fix "in-kernel MMIO" check TDX only supports kernel-initiated MMIO operations. The handle_mmio() function checks if the #VE exception occurred in the kernel and rejects the operation if it did not. However, userspace can deceive the kernel into performing MMIO on its behalf. For example, if userspace can point a syscall to an MMIO address, syscall does get_user() or put_user() on it, triggering MMIO #VE. The kernel will treat the #VE as in-kernel MMIO. Ensure that the target MMIO address is within the kernel before decoding instruction.
Quoted source text, attributed separately from HOL analysis.