CVE-2024-31145
NoneCVSS
—
EPSS
0.2%
Published
Sep 25, 2024
CISA due date
—
Cloudanix analysis
A virtualization bug could let one virtual machine read or change memory it is not supposed to see, potentially exposing data in server or cloud environments.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Moderate
- Impact
- Full Compromise
- Component
- Other
- Class
- Authorization Bypass
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Flawed error handling during setup of Reserved Memory Region (RMRR) or Unity Mapping ranges for PCI devices leaves mappings active after they should have been torn down, granting guest VMs unauthorized access to host memory regions.
Why it matters to the business
Compromised memory isolation in virtualized environments can expose sensitive data or allow privilege escalation across guest boundaries, increasing risk of breaches in multi-tenant or cloud infrastructure.
How an attack unfolds
An attacker with a guest VM that controls a PCI device tied to an RMRR region triggers the flawed mapping logic during device activation; an error condition leaves the mapping in place, after which the guest reads or writes the reserved host memory it should not reach.
How to fix it
Apply the latest hypervisor patches that correct error handling for RMRR and Unity Mapping teardown; verify all affected virtualization software is updated to a version containing the memory-mapping fix.
How to confirm the fix worked
After patching, confirm via hypervisor configuration review and memory-access tests that mappings for RMRR regions are correctly removed when devices are deactivated or guests are shut down.
Typical attack path
- Identify or attach a PCI device associated with an RMRR or Unity Mapping range
- Activate the device to force mapping establishment
- Induce an error path in the mapping logic
- Retain persistent unauthorized mappings
- Access or exfiltrate host memory contents from the guest
How to detect it
Review hypervisor and IOMMU logs for repeated mapping setup errors or unexpected retention of RMRR mappings associated with PCI devices; correlate with guest activity on assigned devices.
What your security team should do
- Prioritize patching of all hypervisors handling PCI passthrough or device assignment
- Audit VM configurations that use direct PCI device assignment
- Disable unnecessary legacy USB emulation or RMRR-dependent features where possible
- Monitor vendor advisories for the specific fixed versions once released
The record
Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. In the logic establishing these mappings, error handling was flawed, resulting in such mappings to potentially remain in place when they should have been removed again. Respective guests would then gain access to memory regions which they aren't supposed to have access to.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Alpine:v3.17 | xen | 0 | 4.16.6-r1 |
| Alpine:v3.18 | xen | 0 | 4.17.5-r0 |
| Alpine:v3.19 | xen | 0 | 4.18.3-r0 |
| Alpine:v3.20 | xen | 0 | 4.18.3-r0 |
| Alpine:v3.21 | xen | 0 | 4.19.0-r0 |
| Alpine:v3.22 | xen | 0 | 4.19.0-r0 |
| Debian:11 | xen | 0 | No fix |
| Debian:12 | xen | 0 | No fix |
| Debian:12 | xen | 0 | 4.17.5+23-ga4e5191dc0-1 |
| Debian:13 | xen | 0 | No fix |
| Debian:13 | xen | 0 | 4.19.1-1 |
| Mageia:9 | xen | 0 | 4.17.5-1.git20251028.1.mga9 |
| SUSE:Enterprise Storage 7.1 | xen | 0 | 4.14.6_18-150300.3.78.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | xen | 0 | 4.13.5_14-150200.3.96.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | xen | 0 | 4.14.6_18-150300.3.78.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise Micro 5.1 | xen | 0 | 4.14.6_18-150300.3.78.1 |
| SUSE:Linux Enterprise Micro 5.2 | xen | 0 | 4.14.6_18-150300.3.78.1 |
| SUSE:Linux Enterprise Micro 5.3 | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise Micro 5.4 | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise Micro 5.5 | xen | 0 | 4.17.5_02-150500.3.36.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP5 | xen | 0 | 4.17.5_02-150500.3.36.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | xen | 0 | 4.18.3_02-150600.3.6.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP5 | xen | 0 | 4.17.5_02-150500.3.36.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP6 | xen | 0 | 4.18.3_02-150600.3.6.1 |
| SUSE:Linux Enterprise Server 12 SP5 | xen | 0 | 4.12.4_52-3.115.1 |
| SUSE:Linux Enterprise Server 12 SP5 | xen | 0 | 4.12.4_56-3.121.1 |
| SUSE:Linux Enterprise Server 15 SP2-LTSS | xen | 0 | 4.13.5_14-150200.3.96.1 |
| SUSE:Linux Enterprise Server 15 SP3-LTSS | xen | 0 | 4.14.6_18-150300.3.78.1 |
| SUSE:Linux Enterprise Server 15 SP4-LTSS | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | xen | 0 | 4.12.4_52-3.115.1 |
| SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | xen | 0 | 4.12.4_56-3.121.1 |
| SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | xen | 0 | 4.13.5_14-150200.3.96.1 |
| SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | xen | 0 | 4.14.6_18-150300.3.78.1 |
| SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | 0 | 4.12.4_52-3.115.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | xen | 0 | 4.12.4_56-3.121.1 |
| SUSE:Manager Proxy 4.3 | xen | 0 | 4.16.6_04-150400.4.62.1 |
| SUSE:Manager Server 4.3 | xen | 0 | 4.16.6_04-150400.4.62.1 |
| Ubuntu:16.04:LTS | xen | 0 | No fix |
| Ubuntu:18.04:LTS | xen | 0 | No fix |
| Ubuntu:20.04:LTS | xen | 0 | No fix |
| Ubuntu:22.04:LTS | xen | 0 | No fix |
| Ubuntu:24.04:LTS | xen | 0 | No fix |
| Ubuntu:24.10 | xen | 0 | No fix |
| Ubuntu:25.04 | xen | 0 | No fix |
| Ubuntu:25.10 | xen | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | xen | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | xen | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | xen | 0 | No fix |
| openSUSE:Leap 15.5 | xen | 0 | 4.17.5_02-150500.3.36.1 |
| openSUSE:Leap 15.6 | xen | 0 | 4.18.3_02-150600.3.6.1 |
| openSUSE:Leap Micro 5.5 | xen | 0 | 4.17.5_02-150500.3.36.1 |
| openSUSE:Tumbleweed | xen | 0 | 4.19.0_02-1.1 |
Related vulnerabilities
- CVE-2024-2201 A cross-privilege Spectre v2 vulnerability allows attackers to bypass all deployed… Also affects xen
- CVE-2024-45818 The hypervisor contains code to accelerate VGA memory accesses for HVM guests, when the… Also affects xen
- CVE-2024-45819 PVH guests have their ACPI tables constructed by the toolstack. Also affects xen
- CVE-2024-45817 In x86's APIC (Advanced Programmable Interrupt Controller) architecture, error conditions… Also affects xen
- CVE-2024-2193 A Speculative Race Condition (SRC) vulnerability that impacts modern CPU architectures… Also affects xen
- CVE-2023-28746 Information exposure through microarchitectural state after transient execution from some… Also affects xen
- CVE-2022-27672 When SMT is enabled, certain AMD processors may speculatively execute instructions using… Also affects xen
- CVE-2019-11135 TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may allow… Also affects xen