What’s Vulnerable › Vulnerabilities
CVE-2026-31719: crypto: krb5enc - fix async decrypt skipping hash verification
- Severity: high (CVSS 7.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-05-01 · updated 2026-10-19
- Weakness: CWE-354
Description
In the Linux kernel, the following vulnerability has been resolved: crypto: krb5enc - fix async decrypt skipping hash verification krb5enc_dispatch_decrypt() sets req->base.complete as the skcipher callback, which is the caller's own completion handler. When the skcipher completes asynchronously, this signals "done" to the caller without executing krb5enc_dispatch_decrypt_hash(), completely bypassing the integrity verification (hash check). Compare with the encrypt path which correctly uses krb5enc_encrypt_done as an intermediate callback to chain into the hash computation on async completion. Fix by adding krb5enc_decrypt_done as an intermediate callback that chains into krb5enc_dispatch_decrypt_hash() upon async skcipher completion, matching the encrypt path's callback pattern. Also fix EBUSY/EINPROGRESS handling throughout: remove krb5enc_request_complete() which incorrectly swallowed EINPROGRESS notifications that must be passed up to callers waiting on backlogged requests, and add missing EBUSY checks in krb5enc_encrypt_ahash_done for the dispatch_encrypt return value. Unset MAY_BACKLOG on the async completion path so the user won't see back-to-back EINPROGRESS notifications.
Affected products
- Linux kernel: from 6.15 before 6.18.25; from 6.19 before 7.0.2; 7.1-rc1 — fixed in 6.18.25, 7.0.2
How to fix
Upgrade to a fixed version: Linux kernel 6.18.25, 7.0.2. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/07cbb1bd424370671814a862913c99a6e1441588
- https://git.kernel.org/stable/c/3bfbf5f0a99c991769ec562721285df7ab69240b
- https://git.kernel.org/stable/c/e51f42114abbdf47f29dda43e7826be28907fcd2
Get alerted when CVE-2026-31719 or the next vulnerability affects your stack