PatchSiren cyber security CVE debrief
CVE-2026-97588 Linux CVE debrief
A Linux kernel vulnerability (CVE-2026-97588) was found where persistent -EBUSY errors during key conversion could lead to indefinite blocking of callers using crypto_wait_req(). The issue has been resolved by translating -EBUSY to -EIO after retry exhaustion. This change ensures proper error propagation and callback invocation, preventing potential system instability. Linux kernel administrators and developers should assess exposure and verify key conversion processes and error handling to maintain system reliability.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Linux kernel administrators and developers, as well as security teams responsible for monitoring and patching Linux systems, should assess exposure and verify key conversion processes and error handling.
Why it matters
CVE-2026-97588 is a Linux kernel vulnerability that could cause indefinite blocking of callers using crypto_wait_req(). Verification of exposure and remediation is necessary to prevent potential system instability.
- Verification of Linux kernel versions and configurations is necessary to determine exposure
- Indefinite blocking of callers using crypto_wait_req() could lead to system instability
- Proper error propagation and callback invocation are crucial for maintaining system reliability
Technical summary
The Linux kernel vulnerability (CVE-2026-97588) involves a situation where hardware persistently returns -EBUSY after exhausting retries, causing the error to propagate to crypto_finalize_*_request(). The crypto API's completion wrapper treats -EBUSY as a queueing status and swallows it, preventing the completion callback from firing. This causes callers using crypto_wait_req() to block indefinitely. The issue has been resolved by translating persistent -EBUSY to -EIO after retry exhaustion to ensure proper error propagation and callback invocation.
Defensive priority
Medium
Recommended defensive actions
- Review Linux kernel configurations and versions to assess exposure
- Verify key conversion processes and error handling
- Monitor for potential blocking issues with crypto_wait_req()
- Perform a thorough review of system logs to identify any instances of indefinite blocking
- Implement additional monitoring to detect similar issues in the future
- Develop a plan to apply vendor patches or mitigations as needed
- Track and document the verification process and any resulting changes
Evidence notes
The CVE record and NVD entry provide details on the Linux kernel vulnerability. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-97588 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-97588
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-97588 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97588
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7a08507ea5b4d06ad8d269287913573f34467565
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e267bd142664a181474112392aeaa8b3d4b12f2e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f6b263679aa72ad2e534bf93db55f2589549a40e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.