CVE-2026-43493: crypto: pcrypt - Fix handling of MAY_BACKLOG requests
In the Linux kernel, the following vulnerability has been resolved:
crypto: pcrypt - Fix handling of MAYBACKLOG requests
MAYBACKLOG requests can return EBUSY. Handle them by checking for that value and filtering out EINPROGRESS notifications.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.7-1Fixed in 7.1.8-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.180-1~deb11u1 - Configuration
Apply the Linux kernel resolution for crypto: pcrypt so that MAY_BACKLOG requests do not return EBUSY (as stated).
Linux kernel crypto/pcrypt handling of MAY_BACKLOG requests = Fix handling of MAY_BACKLOG requests that can return EBUSY - Compensating control
Handle connection notifications by checking for the specific value and filtering out EINPROGRESS notifications (per the provided instruction text).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43493?
The severity of CVE-2026-43493 is critical, with a CVSS score of 9.8.
What type of systems are affected by CVE-2026-43493?
CVE-2026-43493 affects Linux kernel systems using the pcrypt module.
How do I fix CVE-2026-43493?
To fix CVE-2026-43493, update your Linux kernel to a version that includes the security patch addressing this vulnerability.
What does CVE-2026-43493 affect in the Linux kernel?
CVE-2026-43493 affects the handling of MAY_BACKLOG requests in the pcrypt component of the Linux kernel.
What should I do if I cannot update my system to mitigate CVE-2026-43493?
If unable to update, consider implementing temporary workarounds or disabling the affected pcrypt functionality until a patch can be applied.