CVE-2024-47727

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-10-21. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

October 21, 2024

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4008-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
generic

x86/tdx: Fix "in-kernel MMIO" check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d4fc4d01471528da8a9797a065982e05090e1d81
generic

x86/tdx: Fix "in-kernel MMIO" check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bca2e29f7e26ce7c3522f8b324c0bd85612f68e3
generic

x86/tdx: Fix "in-kernel MMIO" check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee
generic

x86/tdx: Fix "in-kernel MMIO" check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25703a3c980e21548774eea8c8a87a75c5c8f58c
generic

x86/tdx: Fix "in-kernel MMIO" check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18ecd5b74682839e7cdafb7cd1ec106df7baa18c

Vendor Advisories for CVE-2024-47727(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1023.25) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1019.23) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-05-23ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1022.22) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1022.25~22.04.2) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1006.8) @ noble2026-05-23ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-54.56.1~22.04.1) @ jammy2026-05-23ubuntu
redhatkernel-0:5.14.0-427.114.1.el9_42026-03-11redhat
redhatkernel-0:5.14.0-570.96.1.el9_62026-03-09redhat
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 6.1.113—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)6.1.115-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.2-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.2-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(15)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-07 08:48 UTCOSV refresh
  3. 2026-09-06 13:46 UTCEPSS rescore
  4. 2026-09-06 13:46 UTCEPSS rescore
  5. 2026-09-04 13:59 UTCEPSS rescore
  6. 2026-09-04 05:05 UTCEPSS rescore
  7. 2026-09-02 14:10 UTCEPSS rescore
  8. 2026-09-01 13:52 UTCEPSS rescore
  9. 2026-09-01 13:52 UTCEPSS rescore
  10. 2026-09-01 04:37 UTCEPSS rescore
  11. 2026-08-30 19:16 UTCEPSS rescore
  12. 2026-08-30 01:20 UTCEPSS rescore
  13. 2026-08-28 21:39 UTCEPSS rescore
  14. 2026-08-27 14:23 UTCEPSS rescore
  15. 2026-08-26 14:44 UTCEPSS rescore
  16. 2026-08-25 13:47 UTCEPSS rescore
  17. 2026-08-24 14:15 UTCEPSS rescore
  18. 2026-08-23 00:18 UTCEPSS rescore
  19. 2026-08-21 23:47 UTCEPSS rescore
  20. 2026-08-20 22:54 UTCEPSS rescore
  21. 2026-08-20 18:31 UTCOSV refresh
  22. 2026-08-19 17:02 UTCEPSS rescore
  23. 2026-08-19 17:02 UTCEPSS rescore
  24. 2026-08-18 13:46 UTCEPSS rescore
  25. 2026-08-17 13:45 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 14:54 UTCEPSS rescore
  2. 2026-08-16 02:13 UTCEPSS rescore
  3. 2026-08-15 01:29 UTCEPSS rescore
  4. 2026-08-13 21:59 UTCEPSS rescore
  5. 2026-08-12 13:49 UTCEPSS rescore
  6. 2026-08-11 13:40 UTCEPSS rescore
  7. 2026-08-10 23:58 UTCEPSS rescore
  8. 2026-08-09 13:45 UTCEPSS rescore
  9. 2026-08-08 16:35 UTCEPSS rescore
  10. 2026-08-07 16:25 UTCEPSS rescore
  11. 2026-08-06 13:45 UTCEPSS rescore
  12. 2026-08-05 19:16 UTCEPSS rescore
  13. 2026-08-05 11:58 UTCEG score recompute
  14. 2026-08-05 11:58 UTCVendor advisory
  15. 2026-08-05 11:58 UTCGHSA enrichment
  16. 2026-08-04 15:08 UTCEPSS rescore
  17. 2026-08-04 11:45 UTCEG score recompute
  18. 2026-08-04 11:45 UTCVendor advisory
  19. 2026-08-04 11:45 UTCGHSA enrichment
  20. 2026-08-04 10:36 UTCEPSS rescore
  21. 2026-08-03 10:34 UTCEPSS rescore
  22. 2026-08-02 02:25 UTCEPSS rescore
  23. 2026-08-01 04:14 UTCEPSS rescore
  24. 2026-08-01 04:14 UTCEPSS rescore
  25. 2026-07-31 15:42 UTCOSV refresh
  26. 2026-07-30 16:26 UTCEPSS rescore
  27. 2026-07-30 01:29 UTCEPSS rescore
  28. 2026-07-28 15:35 UTCEPSS rescore
  29. 2026-07-27 14:11 UTCEPSS rescore
  30. 2026-07-26 14:53 UTCEPSS rescore
  31. 2026-07-26 14:53 UTCEPSS rescore
  32. 2026-07-25 14:17 UTCEPSS rescore
  33. 2026-07-25 14:16 UTCEPSS rescore
  34. 2026-07-24 14:16 UTCEPSS rescore
  35. 2026-07-23 14:17 UTCEPSS rescore
  36. 2026-07-23 14:17 UTCEPSS rescore
  37. 2026-07-23 02:41 UTCEG score recompute
  38. 2026-07-22 14:07 UTCEPSS rescore
  39. 2026-07-22 14:07 UTCEPSS rescore
  40. 2026-07-21 15:23 UTCEPSS rescore
  41. 2026-07-20 17:06 UTCEPSS rescore
  42. 2026-07-19 14:30 UTCEPSS rescore
  43. 2026-07-19 14:30 UTCEPSS rescore
  44. 2026-07-19 02:28 UTCEPSS rescore
  45. 2026-07-19 02:28 UTCEPSS rescore
  46. 2026-07-18 10:03 UTCEPSS rescore
  47. 2026-07-18 10:03 UTCEPSS rescore
  48. 2026-07-16 17:02 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:56 UTCEPSS rescore
  51. 2026-07-15 01:59 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-13 22:55 UTCOSV refresh
  54. 2026-07-13 22:29 UTCEPSS rescore
  55. 2026-07-13 06:12 UTCEPSS rescore
  56. 2026-07-12 05:45 UTCEPSS rescore
  57. 2026-07-12 05:45 UTCEPSS rescore
  58. 2026-07-11 08:26 UTCEPSS rescore
  59. 2026-07-09 19:09 UTCEPSS rescore
  60. 2026-07-09 19:09 UTCEPSS rescore
  61. 2026-07-08 15:14 UTCEPSS rescore
  62. 2026-07-07 13:45 UTCEPSS rescore
  63. 2026-07-06 16:26 UTCEPSS rescore
  64. 2026-07-06 02:22 UTCEPSS rescore
  65. 2026-07-05 02:29 UTCEPSS rescore
  66. 2026-07-04 06:30 UTCEPSS rescore
  67. 2026-07-01 15:05 UTCEPSS rescore
  68. 2026-06-30 23:21 UTCEPSS rescore
  69. 2026-06-29 14:05 UTCEPSS rescore
  70. 2026-06-28 14:07 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-28 04:55 UTCEPSS rescore
  73. 2026-06-27 03:07 UTCEPSS rescore
  74. 2026-06-27 03:07 UTCEPSS rescore
  75. 2026-06-25 20:16 UTCOSV refresh

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-47727?
CVE-2024-47727 is a high vulnerability published on October 21, 2024. 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…
When was CVE-2024-47727 disclosed?
CVE-2024-47727 was first published in the National Vulnerability Database on October 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-47727 actively exploited?
CVE-2024-47727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.1% of all scored CVEs.
What is the CVSS score of CVE-2024-47727?
CVE-2024-47727 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-47727?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-47727, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-47727

Explore →

Is Your Infrastructure Affected by CVE-2024-47727?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs