CVE-2024-26623 Vulnerability Analysis & Exploit Details

CVE-2024-26623
Vulnerability Scoring

7.8
/10
Very High Risk

Highly exploitable, CVE-2024-26623 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-2024-26623 Details

Status: Modified

Last updated: 🕚 04 Aug 2026, 11:16 UTC
Originally published on: 🕖 06 Mar 2024, 07:15 UTC

Time between publication and last update: 881 days

CVSS Release: version 3

CVSS3 Source

416baaa9-dc9f-4396-8d5f-8c081fb06d67

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-26623 Vulnerability Summary

CVE-2024-26623: In the Linux kernel, the following vulnerability has been resolved: pds_core: Prevent race issues involving the adminq There are multiple paths that can result in using the pdsc's adminq. [1] pdsc_adminq_isr and the resulting work from queue_work(), i.e. pdsc_work_thread()->pdsc_process_adminq() [2] pdsc_adminq_post() When the device goes through reset via PCIe reset and/or a fw_down/fw_up cycle due to bad PCIe state or bad device state the adminq is destroyed and recreated. A NULL pointer dereference can happen if [1] or [2] happens after the adminq is already destroyed. In order to fix this, add some further state checks and implement reference counting for adminq uses. Reference counting was used because multiple threads can attempt to access the adminq at the same time via [1] or [2]. Additionally, multiple clients (i.e. pds-vfio-pci) can be using [2] at the same time. The adminq_refcnt is initialized to 1 when the adminq has been allocated and is ready to use. Users/clients of the adminq (i.e. [1] and [2]) will increment the refcnt when they are using the adminq. When the driver goes into a fw_down cycle it will set the PDSC_S_FW_DEAD bit and then wait for the adminq_refcnt to hit 1. Setting the PDSC_S_FW_DEAD before waiting will prevent any further adminq_refcnt increments. Waiting for the adminq_refcnt to hit 1 allows for any current users of the adminq to finish before the driver frees the adminq. Once the adminq_refcnt hits 1 the driver clears the refcnt to signify that the adminq is deleted and cannot be used. On the fw_up cycle the driver will once again initialize the adminq_refcnt to 1 allowing the adminq to be used again.

Assessing the Risk of CVE-2024-26623

Access Complexity Graph

The exploitability of CVE-2024-26623 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-26623

CVE-2024-26623 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-26623, 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-26623, 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-2024-26623 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-26623 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2024-26623 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.07% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 94.93% of others.

CVE-2024-26623 References

External References

CWE Common Weakness Enumeration

CWE-476

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.4:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:rc7:*:*:*:*:*:*
  • 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.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.8:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-26623: 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-2026-90555 – vLLM versions before 0.28.0 fail to validate audio sample rate headers in the transcription endpoint, allowing authenticated clients to bypass dura...
  • CVE-2026-90554 – vLLM versions >=0.10.2 and <0.28.0 do not apply any audio decode-size or duration limit when extracting audio from video input for NanoNemotronVL m...
  • CVE-2026-90553 – vLLM before 0.28.0 contains a remote code execution vulnerability in the LlavaOnevision2 processor loader that ignores the trust_remote_code parame...
  • CVE-2026-90552 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the Playlists_schedules/list.json.php a...
  • CVE-2026-90551 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the video_from_program API endpoint, al...