Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-53135KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN

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.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-53135, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Modified3.1Medium6.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < c3742319d021f5aa3a0a8c828485fee14753f6de
    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < d4b42f926adcce4e5ec193c714afd9d37bba8e5b
    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < b8a1d572478b6f239061ee9578b2451bf2f021c2
    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < e6716f4230a8784957273ddd27326264b27b9313
    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < d28b059ee4779b5102c5da6e929762520510e406
    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < b91bb0ce5cd7005b376eac690ec664c1b56372ec
    • affected f99e3daf94ff35dd4a878d32ff66e1fd35223ad6 – < aa0d42cacf093a6fcca872edc954f6f812926a17
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.4.287 – ≤ 5.4.*
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.119 – ≤ 6.1.*
    • unaffected 6.6.63 – ≤ 6.6.*
    • unaffected 6.11.10 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-53135 badge
[![CVE-2024-53135](https://cveledger.app/badge/CVE-2024-53135.svg)](https://cveledger.app/cve/CVE-2024-53135)

Record last updated .