CVE-2024-26623: pds_core: Prevent race issues involving the adminq
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 22cd6046eb2148b18990257505834dd45c672a1b, 5939feb63ea1f011027576c64b68b681cbad31ca, 7e82a8745b951b1e794cc780d46f3fbee5e93447.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 22cd6046eb2148b18990257505834dd45c672a1b, 5939feb63ea1f011027576c64b68b681cbad31ca, 7e82a8745b951b1e794cc780d46f3fbee5e93447 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 6, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-476
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 7.8
- 3.1 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4 and later · before 6.6.16
- linux linux kernel6.7 and later · before 6.7.4
- linux linux kernel6.8
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.4affected
- 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 22cd6046eb2148b18990257505834dd45c672a1baffected · git
- 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 5939feb63ea1f011027576c64b68b681cbad31caaffected · git
- 01ba61b55b2041a39c54aefb3153c770dd59a0ef and later · before 7e82a8745b951b1e794cc780d46f3fbee5e93447affected · git
- before 6.4not affected · semver
- 6.6.16 and later · up to and including 6.6.*not affected · semver
- 6.7.4 and later · up to and including 6.7.*not affected · semver
- 6.8 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.7.7-1 | 6.7.7-1 |
| openSUSE:Leap 15.6 | dtb-aarch64 | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-64kb | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-debug | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-default | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-default-base | before 6.4.0-150600.23.17.1.150600.12.6.2 | 6.4.0-150600.23.17.1.150600.12.6.2 |
| openSUSE:Leap 15.6 | kernel-docs | before 6.4.0-150600.23.17.3 | 6.4.0-150600.23.17.3 |
| openSUSE:Leap 15.6 | kernel-kvmsmall | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-obs-build | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-obs-qa | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-source | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-syms | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| openSUSE:Leap 15.6 | kernel-zfcpdump | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_3 | before 1-150600.13.3.1 | 1-150600.13.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-64kb | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-default | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-default-base | before 6.4.0-150600.23.17.1.150600.12.6.2 | 6.4.0-150600.23.17.1.150600.12.6.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-source | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-zfcpdump | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | kernel-docs | before 6.4.0-150600.23.17.3 | 6.4.0-150600.23.17.3 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | kernel-obs-build | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | kernel-syms | before 6.4.0-150600.23.17.1 | 6.4.0-150600.23.17.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52606Mar 6, 2024 · powerpc/lib: Validate size for vector operations22Monitor
- ← EarlierCVE-2023-52607Mar 6, 2024 · powerpc/mm: Fix null-pointer dereference in pgtable_cache_add22Monitor
- Later →CVE-2024-26625Mar 6, 2024 · llc: call sock_orphan() at release time31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 22cd6046eb2148b18990257505834dd45c672a1b | Vendor (CNA) |
| Linux Linux | 5939feb63ea1f011027576c64b68b681cbad31ca | Vendor (CNA) |
| Linux Linux | 7e82a8745b951b1e794cc780d46f3fbee5e93447 | Vendor (CNA) |
| debian:linux | 6.7.7-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.17.1.150600.12.6.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-docs | 6.4.0-150600.23.17.3 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 6.4.0-150600.23.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150600.23.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150600.23.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150600.23.17.1.150600.12.6.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150600.23.17.3 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_3 | 1-150600.13.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-obs-build | 6.4.0-150600.23.17.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150600.23.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-syms | 6.4.0-150600.23.17.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-zfcpdump | 6.4.0-150600.23.17.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0180 · Mar 7, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.