CVE-2024-53135KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 8.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before c3742319d021f5aa3a0a8c828485fee14753f6de; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before d4b42f926adcce4e5ec193c714afd9d37bba8e5b; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before b8a1d572478b6f239061ee9578b2451bf2f021c2; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before e6716f4230a8784957273ddd27326264b27b9313; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before d28b059ee4779b5102c5da6e929762520510e406; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before b91bb0ce5cd7005b376eac690ec664c1b56372ec; from f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 before aa0d42cacf093a6fcca872edc954f6f812926a17 | CNA record |
linux linux_kernel linux:linux_kernel | from 5.0 before 6.1.119; from 6.2 before 6.6.63; from 6.7 before 6.11.10; 6.12; 6.12; 6.12; 6.12; 6.12; and 2 more ranges | NVD |
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/e6716f4230a8784957273ddd27326264b27b9313patch
- https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406patch
- https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ecpatch
- https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17patch
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.