CVE-2024-35980 Vulnerability Analysis & Exploit Details

CVE-2024-35980
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-35980 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-35980 Details

Status: Analyzed

Last updated: 🕔 16 Jan 2025, 17:21 UTC
Originally published on: 🕙 20 May 2024, 10:15 UTC

Time between publication and last update: 241 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2024-35980 Vulnerability Summary

CVE-2024-35980: In the Linux kernel, the following vulnerability has been resolved: arm64: tlb: Fix TLBI RANGE operand KVM/arm64 relies on TLBI RANGE feature to flush TLBs when the dirty pages are collected by VMM and the page table entries become write protected during live migration. Unfortunately, the operand passed to the TLBI RANGE instruction isn't correctly sorted out due to the commit 117940aa6e5f ("KVM: arm64: Define kvm_tlb_flush_vmid_range()"). It leads to crash on the destination VM after live migration because TLBs aren't flushed completely and some of the dirty pages are missed. For example, I have a VM where 8GB memory is assigned, starting from 0x40000000 (1GB). Note that the host has 4KB as the base page size. In the middile of migration, kvm_tlb_flush_vmid_range() is executed to flush TLBs. It passes MAX_TLBI_RANGE_PAGES as the argument to __kvm_tlb_flush_vmid_range() and __flush_s2_tlb_range_op(). SCALE#3 and NUM#31, corresponding to MAX_TLBI_RANGE_PAGES, isn't supported by __TLBI_RANGE_NUM(). In this specific case, -1 has been returned from __TLBI_RANGE_NUM() for SCALE#3/2/1/0 and rejected by the loop in the __flush_tlb_range_op() until the variable @scale underflows and becomes -9, 0xffff708000040000 is set as the operand. The operand is wrong since it's sorted out by __TLBI_VADDR_RANGE() according to invalid @scale and @num. Fix it by extending __TLBI_RANGE_NUM() to support the combination of SCALE#3 and NUM#31. With the changes, [-1 31] instead of [-1 30] can be returned from the macro, meaning the TLBs for 0x200000 pages in the above example can be flushed in one shoot with SCALE#3 and NUM#31. The macro TLBI_RANGE_MASK is dropped since no one uses it any more. The comments are also adjusted accordingly.

Assessing the Risk of CVE-2024-35980

Access Complexity Graph

The exploitability of CVE-2024-35980 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-35980

CVE-2024-35980 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-35980, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-35980, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2024-35980 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-35980 poses no threat to data integrity.
  • Availability: High
    CVE-2024-35980 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.042% (probability of exploit)

EPSS Percentile: 5.02% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.98% of others.

CVE-2024-35980 References

External References

CWE Common Weakness Enumeration

CWE-191

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.6:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.20:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.21:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.21:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.22:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.22:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.23:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.23:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.24:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.24:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.25:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.25:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.26:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.26:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.27:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.27:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.28:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.28:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-35980: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...