Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 18ecd5b74682839e7cdafb7cd1ec106df7baa18c, 25703a3c980e21548774eea8c8a87a75c5c8f58c, 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 18ecd5b74682839e7cdafb7cd1ec106df7baa18c, 25703a3c980e21548774eea8c8a87a75c5c8f58c, 4c0c5dcb5471de5fc8f0a1c4980e5815339e1cee; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 16th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-47727

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.19 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.54
  • linux linux kernel6.7 and later · before 6.10.13
  • linux linux kernel6.11 and later · before 6.11.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.19affected
    • 31d58c4e557d46fa7f8557714250fb6f89c941ae and later · before 25703a3c980e21548774eea8c8a87a75c5c8f58caffected · git
    • 31d58c4e557d46fa7f8557714250fb6f89c941ae and later · before 4c0c5dcb5471de5fc8f0a1c4980e5815339e1ceeaffected · git
    • 31d58c4e557d46fa7f8557714250fb6f89c941ae and later · before 18ecd5b74682839e7cdafb7cd1ec106df7baa18caffected · git
    • 31d58c4e557d46fa7f8557714250fb6f89c941ae and later · before bca2e29f7e26ce7c3522f8b324c0bd85612f68e3affected · git
    • 31d58c4e557d46fa7f8557714250fb6f89c941ae and later · before d4fc4d01471528da8a9797a065982e05090e1d81affected · git
    • before 5.19not affected · semver
    • 6.1.113 and later · up to and including 6.1.*not affected · semver
    • 6.6.54 and later · up to and including 6.6.*not affected · semver
    • 6.10.13 and later · up to and including 6.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.2-16.11.2-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.114.1.el9_40:7.3.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-docbefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.114.1.el9_40:5.14.0-427.114.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-47724Oct 21, 2024 · wifi: ath11k: use work queue to process beacon tx event
    22Monitor
  • ← EarlierCVE-2024-47726Oct 21, 2024 · f2fs: fix to wait dio completion
    26Monitor
  • Later →CVE-2024-47728Oct 21, 2024 · bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux18ecd5b74682839e7cdafb7cd1ec106df7baa18cVendor (CNA)
Linux Linux25703a3c980e21548774eea8c8a87a75c5c8f58cVendor (CNA)
Linux Linux4c0c5dcb5471de5fc8f0a1c4980e5815339e1ceeVendor (CNA)
Linux Linuxbca2e29f7e26ce7c3522f8b324c0bd85612f68e3Vendor (CNA)
Linux Linuxd4fc4d01471528da8a9797a065982e05090e1d81Vendor (CNA)
Azure Linux 3.0 ARM6.6.56.1-5 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.56.1-5 · kernelMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-570.96.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-39682319 days aparttls: fix handling of zero-length records on the rx_listKEV
    70This week
  • CVE-2024-4228465 days aparttipc: Return non-zero value from tipc_udp_addr2str() on error
    31Monitor
  • CVE-2024-4215983 days apartscsi: mpi3mr: Sanitise num_phys
    31Monitor
  • CVE-2024-4216083 days apartf2fs: check validation of fault attrs in f2fs_build_fault_attr()
    31Monitor
  • CVE-2021-47014236 days apartnet/sched: act_ct: fix wild memory access when clearing fragments
    31Monitor
  • CVE-2025-38566302 days apartsunrpc: fix handling of server side tls alerts
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-754 · Improper Check for Unusual or Exceptional Conditions

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records