CVE-2026-31719

crypto: krb5enc - fix async decrypt skipping hash verification

State
Published
Severity
7.5 High
Published
May 1, 2026
Updated
Oct 19, 2026
Reserved
Mar 9, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.5 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NLinux

Weaknesses

  • CWE-354 Improper Validation of Integrity Check Value

Affected Products

ProductVersions
LinuxLinux
  • d1775a177f7f38156d541c8a3e3c91eaa6e69699 to before 07cbb1bd424370671814a862913c99a6e1441588Affected
  • d1775a177f7f38156d541c8a3e3c91eaa6e69699 to before e51f42114abbdf47f29dda43e7826be28907fcd2Affected
  • d1775a177f7f38156d541c8a3e3c91eaa6e69699 to before 3bfbf5f0a99c991769ec562721285df7ab69240bAffected
LinuxLinux
  • 6.15Affected
  • before 6.15Not affected
  • 6.18.25 through 6.18.*Not affected
  • 7.0.2 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.