Medium [CVE-2026-64148] fix error handling in pdsc_devcmd_wait
This medium-severity Red Hat Linux advisory covers CVE-2026-64148.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
This vulnerability involves incorrect error handling within the pdsc_devcmd_wait function, which can cause the system to report a successful operation even when a firmware crash or command timeout has occurred. This misreporting can prevent proper error propagation and delay recovery actions, potentially leading to system instability or unexpected behavior.
The issue stems from the function returning stale success status instead of an actual error, hindering the detection and resolution of underlying hardware or command processing problems. Red Hat severity: Moderate.
Weakness: CWE-393.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · medium-confidence parse· fetched 6 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 6 days ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 6 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.