Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-47727x86/tdx: Fix "in-kernel MMIO" check

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47727, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.25% · top 84% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 31d58c4e557d46fa7f8557714250fb6f89c941ae – < 25703a3c980e21548774eea8c8a87a75c5c8f58c
    • affected 31d58c4e557d46fa7f8557714250fb6f89c941ae – < 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee
    • affected 31d58c4e557d46fa7f8557714250fb6f89c941ae – < 18ecd5b74682839e7cdafb7cd1ec106df7baa18c
    • affected 31d58c4e557d46fa7f8557714250fb6f89c941ae – < bca2e29f7e26ce7c3522f8b324c0bd85612f68e3
    • affected 31d58c4e557d46fa7f8557714250fb6f89c941ae – < d4fc4d01471528da8a9797a065982e05090e1d81
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.54 – ≤ 6.6.*
    • unaffected 6.10.13 – ≤ 6.10.*
    • unaffected 6.11.2 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47727 badge
[![CVE-2024-47727](https://cveledger.app/badge/CVE-2024-47727.svg)](https://cveledger.app/cve/CVE-2024-47727)

Record last updated .