cve-2024-53135
Vulnerability from cvelistv5
Published
2024-12-04 14:20
Modified
2024-12-19 09:40
Severity ?
EPSS score ?
0.04% (0.08518)
Summary
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.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b8a1d572478b6f239061ee9578b2451bf2f021c2
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ecPatch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c3742319d021f5aa3a0a8c828485fee14753f6de
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d4b42f926adcce4e5ec193c714afd9d37bba8e5b
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e6716f4230a8784957273ddd27326264b27b9313Patch
Impacted products
Vendor Product Version
Linux Linux Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
Version: f99e3daf94ff35dd4a878d32ff66e1fd35223ad6
 Create a notification for this product.
   Linux Linux Version: 5.0
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "arch/x86/kvm/vmx/vmx.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "c3742319d021f5aa3a0a8c828485fee14753f6de",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
                  {
                     lessThan: "d4b42f926adcce4e5ec193c714afd9d37bba8e5b",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
                  {
                     lessThan: "b8a1d572478b6f239061ee9578b2451bf2f021c2",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
                  {
                     lessThan: "e6716f4230a8784957273ddd27326264b27b9313",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
                  {
                     lessThan: "d28b059ee4779b5102c5da6e929762520510e406",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
                  {
                     lessThan: "b91bb0ce5cd7005b376eac690ec664c1b56372ec",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
                  {
                     lessThan: "aa0d42cacf093a6fcca872edc954f6f812926a17",
                     status: "affected",
                     version: "f99e3daf94ff35dd4a878d32ff66e1fd35223ad6",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "arch/x86/kvm/vmx/vmx.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "5.0",
                  },
                  {
                     lessThan: "5.0",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.4.*",
                     status: "unaffected",
                     version: "5.4.287",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.10.*",
                     status: "unaffected",
                     version: "5.10.231",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.15.*",
                     status: "unaffected",
                     version: "5.15.174",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.1.*",
                     status: "unaffected",
                     version: "6.1.119",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.6.*",
                     status: "unaffected",
                     version: "6.6.63",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.11.*",
                     status: "unaffected",
                     version: "6.11.10",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "6.12",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN\n\nHide KVM's pt_mode module param behind CONFIG_BROKEN, i.e. disable support\nfor virtualizing Intel PT via guest/host mode unless BROKEN=y.  There are\nmyriad bugs in the implementation, some of which are fatal to the guest,\nand others which put the stability and health of the host at risk.\n\nFor guest fatalities, the most glaring issue is that KVM fails to ensure\ntracing is disabled, and *stays* disabled prior to VM-Enter, which is\nnecessary as hardware disallows loading (the guest's) RTIT_CTL if tracing\nis enabled (enforced via a VMX consistency check).  Per the SDM:\n\n  If the logical processor is operating with Intel PT enabled (if\n  IA32_RTIT_CTL.TraceEn = 1) at the time of VM entry, the \"load\n  IA32_RTIT_CTL\" VM-entry control must be 0.\n\nOn the host side, KVM doesn't validate the guest CPUID configuration\nprovided by userspace, and even worse, uses the guest configuration to\ndecide what MSRs to save/load at VM-Enter and VM-Exit.  E.g. configuring\nguest CPUID to enumerate more address ranges than are supported in hardware\nwill result in KVM trying to passthrough, save, and load non-existent MSRs,\nwhich generates a variety of WARNs, ToPA ERRORs in the host, a potential\ndeadlock, etc.",
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-12-19T09:40:03.779Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/c3742319d021f5aa3a0a8c828485fee14753f6de",
            },
            {
               url: "https://git.kernel.org/stable/c/d4b42f926adcce4e5ec193c714afd9d37bba8e5b",
            },
            {
               url: "https://git.kernel.org/stable/c/b8a1d572478b6f239061ee9578b2451bf2f021c2",
            },
            {
               url: "https://git.kernel.org/stable/c/e6716f4230a8784957273ddd27326264b27b9313",
            },
            {
               url: "https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406",
            },
            {
               url: "https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ec",
            },
            {
               url: "https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17",
            },
         ],
         title: "KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-53135",
      datePublished: "2024-12-04T14:20:40.815Z",
      dateReserved: "2024-11-19T17:17:24.996Z",
      dateUpdated: "2024-12-19T09:40:03.779Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-53135\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-04T15:15:13.630\",\"lastModified\":\"2024-12-14T21:15:37.547\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN\\n\\nHide KVM's pt_mode module param behind CONFIG_BROKEN, i.e. disable support\\nfor virtualizing Intel PT via guest/host mode unless BROKEN=y.  There are\\nmyriad bugs in the implementation, some of which are fatal to the guest,\\nand others which put the stability and health of the host at risk.\\n\\nFor guest fatalities, the most glaring issue is that KVM fails to ensure\\ntracing is disabled, and *stays* disabled prior to VM-Enter, which is\\nnecessary as hardware disallows loading (the guest's) RTIT_CTL if tracing\\nis enabled (enforced via a VMX consistency check).  Per the SDM:\\n\\n  If the logical processor is operating with Intel PT enabled (if\\n  IA32_RTIT_CTL.TraceEn = 1) at the time of VM entry, the \\\"load\\n  IA32_RTIT_CTL\\\" VM-entry control must be 0.\\n\\nOn the host side, KVM doesn't validate the guest CPUID configuration\\nprovided by userspace, and even worse, uses the guest configuration to\\ndecide what MSRs to save/load at VM-Enter and VM-Exit.  E.g. configuring\\nguest CPUID to enumerate more address ranges than are supported in hardware\\nwill result in KVM trying to passthrough, save, and load non-existent MSRs,\\nwhich generates a variety of WARNs, ToPA ERRORs in the host, a potential\\ndeadlock, etc.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: KVM: VMX: oculta la virtualización de Intel PT (modo invitado/host) detrás de CONFIG_BROKEN Oculta el parámetro del módulo pt_mode de KVM detrás de CONFIG_BROKEN, es decir, deshabilita la compatibilidad con la virtualización de Intel PT a través del modo invitado/host a menos que BROKEN=y. Hay una gran cantidad de errores en la implementación, algunos de los cuales son fatales para el invitado y otros que ponen en riesgo la estabilidad y la salud del host. Para las fatalidades del invitado, el problema más evidente es que KVM no garantiza que el seguimiento esté deshabilitado y *permanece* deshabilitado antes de VM-Enter, lo que es necesario ya que el hardware no permite cargar RTIT_CTL (del invitado) si el seguimiento está habilitado (lo que se aplica a través de una verificación de consistencia de VMX). Según el SDM: si el procesador lógico está funcionando con Intel PT habilitado (si IA32_RTIT_CTL.TraceEn = 1) en el momento de la entrada de la VM, el control de entrada de la VM \\\"cargar IA32_RTIT_CTL\\\" debe ser 0. En el lado del host, KVM no valida la configuración de CPUID del invitado proporcionada por el espacio de usuario y, lo que es peor, utiliza la configuración del invitado para decidir qué MSR guardar/cargar en VM-Enter y VM-Exit. Por ejemplo, configurar la CPUID del invitado para enumerar más rangos de direcciones de los que admite el hardware hará que KVM intente pasar, guardar y cargar MSR inexistentes, lo que genera una variedad de WARN, ERRORES ToPA en el host, un posible bloqueo, etc.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.0,\"impactScore\":4.0}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.0\",\"versionEndExcluding\":\"6.1.119\",\"matchCriteriaId\":\"8D57FCD1-3F44-46BA-AC05-0FF305BED53B\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.63\",\"matchCriteriaId\":\"8800BB45-48BC-4B52-BDA5-B1E4633F42E5\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.11.10\",\"matchCriteriaId\":\"C256F46A-AFDD-4B99-AA4F-67D9D9D2C55A\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"7F361E1D-580F-4A2D-A509-7615F73167A1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"3C95E234-D335-4B6C-96BF-E2CEBD8654ED\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"E0F717D8-3014-4F84-8086-0124B2111379\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"24DBE6C7-2AAE-4818-AED2-E131F153D2FA\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"24B88717-53F5-42AA-9B72-14C707639E3F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc7:*:*:*:*:*:*\",\"matchCriteriaId\":\"1EF8CD82-1EAE-4254-9545-F85AB94CF90F\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/b8a1d572478b6f239061ee9578b2451bf2f021c2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ec\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c3742319d021f5aa3a0a8c828485fee14753f6de\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/d4b42f926adcce4e5ec193c714afd9d37bba8e5b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e6716f4230a8784957273ddd27326264b27b9313\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.