CVE-2026-64148
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 0.5% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.5% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.5% · EPSS, next 30 days
- Weakness
- CWE-835
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6.142
- Linux Kernel < 6.12.92
- Linux Kernel < 6.18.34
- Linux Kernel < 7.0.11
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64148.md and follow it. Check whether this project is affected by CVE-2026-64148. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0e46b6635b03d29807f810c3b415c4755a3f958d
- https://git.kernel.org/stable/c/10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2
- https://git.kernel.org/stable/c/3231aff8ab26111c54e630b1a200fc43a729dd14
- https://git.kernel.org/stable/c/560d559324169fe0583d54c475b5329550a86f71
- https://git.kernel.org/stable/c/784dd2bdc622ed3cc6ef8e113aa1852e252de36f
References
- https://git.kernel.org/stable/c/0e46b6635b03d29807f810c3b415c4755a3f958d
- https://git.kernel.org/stable/c/10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2
- https://git.kernel.org/stable/c/3231aff8ab26111c54e630b1a200fc43a729dd14
- https://git.kernel.org/stable/c/560d559324169fe0583d54c475b5329550a86f71
- https://git.kernel.org/stable/c/784dd2bdc622ed3cc6ef8e113aa1852e252de36f