CVE-2025-38554 Vulnerability Analysis & Exploit Details

CVE-2025-38554
Vulnerability Scoring

7.8
/10
Very High Risk

Highly exploitable, CVE-2025-38554 poses a critical security risk that could lead to severe breaches.

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-38554 Details

Status: Analyzed

Last updated: 🕠 18 Nov 2025, 17:59 UTC
Originally published on: 🕔 19 Aug 2025, 17:15 UTC

Time between publication and last update: 91 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:H/I:H/A:H

CVE-2025-38554 Vulnerability Summary

CVE-2025-38554: In the Linux kernel, the following vulnerability has been resolved: mm: fix a UAF when vma->mm is freed after vma->vm_refcnt got dropped By inducing delays in the right places, Jann Horn created a reproducer for a hard to hit UAF issue that became possible after VMAs were allowed to be recycled by adding SLAB_TYPESAFE_BY_RCU to their cache. Race description is borrowed from Jann's discovery report: lock_vma_under_rcu() looks up a VMA locklessly with mas_walk() under rcu_read_lock(). At that point, the VMA may be concurrently freed, and it can be recycled by another process. vma_start_read() then increments the vma->vm_refcnt (if it is in an acceptable range), and if this succeeds, vma_start_read() can return a recycled VMA. In this scenario where the VMA has been recycled, lock_vma_under_rcu() will then detect the mismatching ->vm_mm pointer and drop the VMA through vma_end_read(), which calls vma_refcount_put(). vma_refcount_put() drops the refcount and then calls rcuwait_wake_up() using a copy of vma->vm_mm. This is wrong: It implicitly assumes that the caller is keeping the VMA's mm alive, but in this scenario the caller has no relation to the VMA's mm, so the rcuwait_wake_up() can cause UAF. The diagram depicting the race: T1 T2 T3 == == == lock_vma_under_rcu mas_walk <VMA gets removed from mm> mmap <the same VMA is reallocated> vma_start_read __refcount_inc_not_zero_limited_acquire munmap __vma_enter_locked refcount_add_not_zero vma_end_read vma_refcount_put __refcount_dec_and_test rcuwait_wait_event <finish operation> rcuwait_wake_up [UAF] Note that rcuwait_wait_event() in T3 does not block because refcount was already dropped by T1. At this point T3 can exit and free the mm causing UAF in T1. To avoid this we move vma->vm_mm verification into vma_start_read() and grab vma->vm_mm to stabilize it before vma_refcount_put() operation. [surenb@google.com: v3]

Assessing the Risk of CVE-2025-38554

Access Complexity Graph

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

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

  • Confidentiality: High
    Exploiting CVE-2025-38554 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-38554 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2025-38554 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-38554 References

External References

CWE Common Weakness Enumeration

CWE-416

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.15:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.15.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.15.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.16:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.16:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-38554: 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-13735 – Out-of-bounds Read vulnerability in ASR1903、ASR3901 in ASR Lapwing_Linux on Linux (nr_fw modules). This vulnerability is associated with program fi...
  • CVE-2025-9558 – There is a potential OOB Write vulnerability in the gen_prov_start function in pb_adv.c. The full length of the received data is copied into the li...
  • CVE-2025-9557 – ‭An out-of-bound write can lead to an arbitrary code execution. Even on devices with some form of memory protection, this can still lead to‬ ‭a cra...
  • CVE-2025-59820 – In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import.cpp (ak...
  • CVE-2025-55174 – In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the beginning followed by the partial co...