CVE-2026-64148: pds_core: fix error handling in pdsc_devcmd_wait
Noroxi assessment
Priority: Monitor (action score 30/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.46% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0e46b6635b03d29807f810c3b415c4755a3f958d, 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2, 3231aff8ab26111c54e630b1a200fc43a729dd14.
Low priority for now. Upgrade to Linux Linux 0e46b6635b03d29807f810c3b415c4755a3f958d, 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2, 3231aff8ab26111c54e630b1a200fc43a729dd14 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: fix error handling in pdsc_devcmd_wait Fix two cases where pdsc_devcmd_wait() returns stale success from the completion register instead of an error: 1. FW crash: If firmware stops running, the wait loop breaks early with running=false. The condition "if ((!done || timeout) && running)" is false, so error handling is bypassed and stale status is returned. Check !running first and return -ENXIO. 2. Timeout: If a command times out, err is set to -ETIMEDOUT but then overwritten by pdsc_err_to_errno(status) which reads stale status. Return -ETIMEDOUT immediately after cleaning up. Both errors now propagate to pdsc_devcmd_locked() which queues health_work for recovery.
- Published
- Jul 19, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-835
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
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.142
- linux linux kernel6.7 and later · before 6.12.92
- linux linux kernel6.13 and later · before 6.18.34
- linux linux kernel6.19 and later · before 7.0.11
- linux linux kernel7.1
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
- 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and later · before 3231aff8ab26111c54e630b1a200fc43a729dd14affected · git
- 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and later · before 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2affected · git
- 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and later · before 784dd2bdc622ed3cc6ef8e113aa1852e252de36faffected · git
- 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and later · before 560d559324169fe0583d54c475b5329550a86f71affected · git
- 45d76f492938cdc27ddadc16e1e75103f4cfbf56 and later · before 0e46b6635b03d29807f810c3b415c4755a3f958daffected · git
- before 6.4not affected · semver
- 6.6.142 and later · up to and including 6.6.*not affected · semver
- 6.12.92 and later · up to and including 6.12.*not affected · semver
- 6.18.34 and later · up to and including 6.18.*not affected · semver
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.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-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-2026-64145Jul 19, 2026 · wifi: wilc1000: fix dma_buffer leak on bus acquire failure31Monitor
- ← EarlierCVE-2026-64147Jul 19, 2026 · pds_core: fix debugfs_lookup dentry leak and error handling22Monitor
- Later →CVE-2026-64149Jul 19, 2026 · dma-mapping: move dma_map_resource() sanity check into debug code22Monitor
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 | 0e46b6635b03d29807f810c3b415c4755a3f958d | Vendor (CNA) |
| Linux Linux | 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2 | Vendor (CNA) |
| Linux Linux | 3231aff8ab26111c54e630b1a200fc43a729dd14 | Vendor (CNA) |
| Linux Linux | 560d559324169fe0583d54c475b5329550a86f71 | Vendor (CNA) |
| Linux Linux | 784dd2bdc622ed3cc6ef8e113aa1852e252de36f | Vendor (CNA) |
| debian:linux | 6.12.94-1 · Debian:13 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- CVE-2026-3144888 days apartext4: avoid infinite loops caused by residual data37Monitor
- CVE-2026-638890 days apartscsi: scsi_transport_fc: Widen FPIN pname walker counter to u3232Monitor
- CVE-2026-5293325 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()31Monitor
- CVE-2026-639680 days apartipv6: fix possible infinite loop in fib6_select_path()30Monitor
- CVE-2026-4605253 days apartceph: only d_add() negative dentries when they are unhashed30Monitor
- CVE-2026-3155286 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom30Monitor
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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.