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

Published Oct 21, 2024
·
Updated

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 handlemmio() 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 getuser() or putuser() 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.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

10 affected componentsFixes available
Linux Linux kernel>=5.19<6.1.113
Linux Linux kernel>=6.2<6.6.54
Linux Linux kernel>=6.7<6.10.13
Linux Linux kernel>=6.11<6.11.2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1
debian/linux-6.1
6.1.129-1~deb11u1
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade Linux kernel (x86/tdx) to a version that resolves this vulnerability.

    Patch x86/tdx: Fix "in-kernel MMIO" check
  4. Configuration

    Update the TDX MMIO handling logic (handle_mmio()) to check whether the #VE exception occurred in-kernel, and reject the MMIO operation if it did not; do not treat user-triggered #VE as in-kernel MMIO.

    Linux kernel TDX (handle_mmio) in-kernel MMIO check for #VE = Reject MMIO operation unless #VE occurred in the kernel

Event History

Oct 21, 2024
CVE Published
via MITRE·12:14 PM
Data Sourced
via MITRE·12:14 PM
Description
Data Sourced
via Red Hat·01:06 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·01:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 20, 2025
Data Sourced
via Launchpad·12:46 AM
Description
Apr 9, 2025
Data Sourced
via Ubuntu·12:57 AM
RemedyDescriptionSeverityAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-47727?

CVE-2024-47727 is classified as a high severity vulnerability that affects the Linux kernel.

2

How do I fix CVE-2024-47727?

To mitigate CVE-2024-47727, users should update to the latest stable version of the Linux kernel that includes the fix.

3

Who is affected by CVE-2024-47727?

CVE-2024-47727 affects users running specific versions of the Linux kernel between 5.19 and 6.11.

4

What are the potential impacts of CVE-2024-47727?

Exploitation of CVE-2024-47727 could lead to unauthorized access and control over system resources in kernel-initiated MMIO operations.

5

When was CVE-2024-47727 discovered?

CVE-2024-47727 was identified and documented as a vulnerability in the Linux kernel prior to its resolution in recent updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203