CVE-2026-93156: crypto: rk3288 - fail ahash requests on HASH idle timeout
crypto: rk3288 - fail ahash requests on HASH idle timeout
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.157.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.157 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.110 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.52 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.6 - Compensating control
In rk_hash_run(), store the RK_CRYPTO_HASH_STS idle-poll result and finalize the ahash request with the timeout error before reading the digest registers.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel's rk3288 cryptographic hash driver are exposed when the hardware hash engine fails to become idle after a final DMA transfer. The provided data does not identify affected kernel versions or configurations.
What must occur for the incorrect success result to be returned?
The RK3288 hash engine must fail to reach the idle state while rk_hash_run() is polling after the final DMA transfer. In that condition, the vulnerable driver can read digest registers and finalize the hash request using its prior success status instead of reporting the timeout.
How can administrators determine whether they may be affected?
Review whether the running kernel includes the rk3288 crypto hash driver and whether its rk_hash_run() path propagates a HASH idle polling timeout before reading digest registers. The referenced stable commits contain the resolved behavior.