CVE-2025-22023 Vulnerability Analysis & Exploit Details

CVE-2025-22023
Vulnerability Scoring

7.8
/10
Very High Risk

Highly exploitable, CVE-2025-22023 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-22023 Details

Status: Analyzed

Last updated: 🕡 28 Oct 2025, 18:53 UTC
Originally published on: 🕚 16 Apr 2025, 11:15 UTC

Time between publication and last update: 195 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-22023 Vulnerability Summary

CVE-2025-22023: In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Don't skip on Stopped - Length Invalid Up until commit d56b0b2ab142 ("usb: xhci: ensure skipped isoc TDs are returned when isoc ring is stopped") in v6.11, the driver didn't skip missed isochronous TDs when handling Stoppend and Stopped - Length Invalid events. Instead, it erroneously cleared the skip flag, which would cause the ring to get stuck, as future events won't match the missed TD which is never removed from the queue until it's cancelled. This buggy logic seems to have been in place substantially unchanged since the 3.x series over 10 years ago, which probably speaks first and foremost about relative rarity of this case in normal usage, but by the spec I see no reason why it shouldn't be possible. After d56b0b2ab142, TDs are immediately skipped when handling those Stopped events. This poses a potential problem in case of Stopped - Length Invalid, which occurs either on completed TDs (likely already given back) or Link and No-Op TRBs. Such event won't be recognized as matching any TD (unless it's the rare Link TRB inside a TD) and will result in skipping all pending TDs, giving them back possibly before they are done, risking isoc data loss and maybe UAF by HW. As a compromise, don't skip and don't clear the skip flag on this kind of event. Then the next event will skip missed TDs. A downside of not handling Stopped - Length Invalid on a Link inside a TD is that if the TD is cancelled, its actual length will not be updated to account for TRBs (silently) completed before the TD was stopped. I had no luck producing this sequence of completion events so there is no compelling demonstration of any resulting disaster. It may be a very rare, obscure condition. The sole motivation for this patch is that if such unlikely event does occur, I'd rather risk reporting a cancelled partially done isoc frame as empty than gamble with UAF. This will be fixed more properly by looking at Stopped event's TRB pointer when making skipping decisions, but such rework is unlikely to be backported to v6.12, which will stay around for a few years.

Assessing the Risk of CVE-2025-22023

Access Complexity Graph

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

CVE-2025-22023 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-22023, 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-22023, 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-22023 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-22023 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2025-22023 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-22023 References

External References

CWE Common Weakness Enumeration

CWE-416

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.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.9:*:*:*:*:*:*:*
  • 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.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.11.11:*:*:*:*:*:*:*
  • 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.12.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.20:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.21:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.21:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.13.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.13.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.14:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-22023: 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...