CVE-2026-64312: crypto: pcrypt - restore callback for non-parallel fallback
In the Linux kernel, the following vulnerability has been resolved:
crypto: pcrypt - restore callback for non-parallel fallback
pcrypt installs pcryptaeaddone() on the child AEAD request before trying to submit it through padata. If padatadoparallel() returns -EBUSY, pcrypt falls back to calling the child AEAD directly.
That fallback must not keep the padata completion callback. Otherwise an asynchronous completion runs pcryptaeaddone() even though the request was never enrolled in padata.
Restore the original request callback and callback data before calling the child AEAD directly. This keeps the fallback path aligned with a direct AEAD request while leaving the parallel path unchanged.
Affected Software
Remediation
Event History
Frequently Asked Questions
Under what condition is the vulnerable path reached?
The issue occurs when pcrypt submits a child AEAD request through padata and padata_do_parallel() returns -EBUSY. pcrypt then takes its non-parallel fallback path and calls the child AEAD request directly.
What is required for exploitation?
The supplied severity vector indicates that the issue is network-reachable, has low attack complexity, requires no privileges, and needs no user interaction. The description does not identify a specific application, protocol, or configuration that causes the affected fallback condition.
What is the impact of the flaw?
An asynchronous child AEAD completion can invoke pcrypt_aead_done() even though the request was not enrolled in padata. The provided assessment identifies an availability impact only, with no stated confidentiality or integrity impact.
What can be done if patching cannot be performed immediately?
The provided information identifies no workaround or configuration-based mitigation. Applying an available patch is the stated remedy.