CVE-2024-53135: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-7gvv-gph6-2hpj
Share
CVSS 6.5
Published
Advisory Summary

CVE-2024-53135 is a MODERATE (CVSS 6.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2024-53135 at a Glance

CVE Identifier CVE-2024-53135
GHSA Identifier GHSA-7gvv-gph6-2hpj
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2024-53135

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2024-53135, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

NVD — CVE-2024-53135 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-53135
git.kernel.org/stable/c/aa0d42cacf... WEB
https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17
git.kernel.org/stable/c/b8a1d57247... WEB
https://git.kernel.org/stable/c/b8a1d572478b6f239061ee9578b2451bf2f021c2
git.kernel.org/stable/c/b91bb0ce5c... WEB
https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ec
git.kernel.org/stable/c/c3742319d0... WEB
https://git.kernel.org/stable/c/c3742319d021f5aa3a0a8c828485fee14753f6de
git.kernel.org/stable/c/d28b059ee4... WEB
https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406
git.kernel.org/stable/c/d4b42f926a... WEB
https://git.kernel.org/stable/c/d4b42f926adcce4e5ec193c714afd9d37bba8e5b
git.kernel.org/stable/c/e6716f4230... WEB
https://git.kernel.org/stable/c/e6716f4230a8784957273ddd27326264b27b9313
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html

Frequently Asked Questions

What is CVE-2024-53135?
CVE-2024-53135 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2024-53135?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2024-53135?
CVE-2024-53135 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H.
What CWE is associated with CVE-2024-53135?
CVE-2024-53135 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2024-53135?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7gvv-gph6-2hpj",
  "modified" : "2025-11-04T00:32:09Z",
  "published" : "2024-12-04T15:31:52Z",
  "aliases" : [ "CVE-2024-53135" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-53135"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aa0d42cacf093a6fcca872edc954f6f812926a17"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b8a1d572478b6f239061ee9578b2451bf2f021c2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b91bb0ce5cd7005b376eac690ec664c1b56372ec"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c3742319d021f5aa3a0a8c828485fee14753f6de"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d28b059ee4779b5102c5da6e929762520510e406"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d4b42f926adcce4e5ec193c714afd9d37bba8e5b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e6716f4230a8784957273ddd27326264b27b9313"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2024-12-04T15:15:13Z"
  }
}