CVE-2025-21644 Vulnerability Analysis & Exploit Details

CVE-2025-21644
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2025-21644 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-2025-21644 Details

Status: Analyzed

Last updated: 🕞 31 Jan 2025, 15:55 UTC
Originally published on: 🕚 19 Jan 2025, 11:15 UTC

Time between publication and last update: 12 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-2025-21644 Vulnerability Summary

CVE-2025-21644: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix tlb invalidation when wedging If GuC fails to load, the driver wedges, but in the process it tries to do stuff that may not be initialized yet. This moves the xe_gt_tlb_invalidation_init() to be done earlier: as its own doc says, it's a software-only initialization and should had been named with the _early() suffix. Move it to be called by xe_gt_init_early(), so the locks and seqno are initialized, avoiding a NULL ptr deref when wedging: xe 0000:03:00.0: [drm] *ERROR* GT0: load failed: status: Reset = 0, BootROM = 0x50, UKernel = 0x00, MIA = 0x00, Auth = 0x01 xe 0000:03:00.0: [drm] *ERROR* GT0: firmware signature verification failed xe 0000:03:00.0: [drm] *ERROR* CRITICAL: Xe has declared device 0000:03:00.0 as wedged. ... BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 9 UID: 0 PID: 3908 Comm: modprobe Tainted: G U W 6.13.0-rc4-xe+ #3 Tainted: [U]=USER, [W]=WARN Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-S ADP-S DDR5 UDIMM CRB, BIOS ADLSFWI1.R00.3275.A00.2207010640 07/01/2022 RIP: 0010:xe_gt_tlb_invalidation_reset+0x75/0x110 [xe] This can be easily triggered by poking the GuC binary to force a signature failure. There will still be an extra message, xe 0000:03:00.0: [drm] *ERROR* GT0: GuC mmio request 0x4100: no reply 0x4100 but that's better than a NULL ptr deref. (cherry picked from commit 5001ef3af8f2c972d6fd9c5221a8457556f8bea6)

Assessing the Risk of CVE-2025-21644

Access Complexity Graph

The exploitability of CVE-2025-21644 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-2025-21644

CVE-2025-21644 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-2025-21644, 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-2025-21644, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2025-21644 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2025-21644 poses no threat to data integrity.
  • Availability: High
    CVE-2025-21644 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.043% (probability of exploit)

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

CVE-2025-21644 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.11:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:rc6:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-21644: 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-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...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...