CVE-2026-31719
Last modified
CVE-2026-31719 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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.. EPSS estimates a 0.29% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.15, < 6.18.25 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.2 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-31719?
How severe is CVE-2026-31719?
How do I fix CVE-2026-31719?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31713In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31714In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31715In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31716In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31717In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-31718In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-3172Buffer overflow in parallel HNSW index build in pgvector 0.6…8.1
- CVE-2026-31720In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31721In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31722In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31723In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31724In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-31719?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
