CVE-2026-64439
kernel: crypto: krb5 - filter out async aead implementations at alloc
Overview
Description
In the Linux kernel, the following vulnerability has been resolved:
crypto: krb5 - filter out async aead implementations at alloc
krb5_aead_encrypt(), krb5_aead_decrypt() in rfc3961_simplified.c and
rfc8009_encrypt(), rfc8009_decrypt() in rfc8009_aes2.c set a NULL
completion callback and treat any negative return from
crypto_aead_{encrypt,decrypt}() as terminal, falling through to
kfree_sensitive(buffer). When the encrypt_name resolves to an
async AEAD instance the request returns -EINPROGRESS, the buffer
is freed while the backend's worker still holds a pointer, and the
worker dereferences the freed slab on completion.
KASAN report under UML+SLUB with a synthetic async aead backend
bound to krb5->encrypt_name:
BUG: KASAN: slab-use-after-free in t5_stub_complete+0x7d/0xc7
The helpers were written synchronously, so filter the async
instances out at allocation time instead of plumbing
crypto_wait_req() through every call site.
Reachable via net/rxrpc/rxgk.c, fs/afs/cm_security.c and
net/ceph/crypto.c on systems with an async AEAD provider bound to
the krb5 enctype name.
Source: OX vulnerability database
Severity
9.8 · CRITICAL
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-416
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 22 fixes
Red Hat 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 9 | bpftool +105 | wont fix | — |
| 9 | kernel +58 | 0:5.14.0-427.136.1.el9_4 | RHSA-2026:36767 |
| 9 | bpftool | 0:7.3.0-427.136.1.el9_4 | RHSA-2026:36767 |
debian 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 14 | linux | 7.1.4-1 |
openSUSE 1 release · 1 package
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | kernel-devel +3 | 7.1.7-1.1 | openSUSE-SU-2026:11476-1 |
ubuntu 2 releases · 17 packages
| Release | Package | Fixed in |
|---|---|---|
| 24.04 | linux-gcp-7-0 +1 | 7.0.0-1011.11~24.04.1 |
| 24.04 | linux-aws-7-0 | 7.0.0-1012.12~24.04.1 |
| 24.04 | linux-azure-fde-7-0 | 7.0.0-1013.13~24.04.1 |
| 24.04 | linux-azure-7-0 | 7.0.0-1014.14~24.04.1 |
| 24.04 | linux-nvidia-7-0 | 7.0.0-1018.18~24.04.1 |
| 24.04 | linux-riscv-7-0 | 7.0.0-31.31.1~24.04.1 |
11 more rows
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2026-64439
- git.kernel.org https://git.kernel.org/linus/6c9dddeb582fde005360f4fe02c760d45ca05fb5 (7.2-rc1)
- git.kernel.org https://git.kernel.org/stable/c/2b7bd6dccff14b8b632c5244f1fd506918077221
- git.kernel.org https://git.kernel.org/stable/c/6c9dddeb582fde005360f4fe02c760d45ca05fb5
- git.kernel.org https://git.kernel.org/stable/c/ef6feb77e2d91761427c5b773edc9c97e1b706ad
- lore.kernel.org https://lore.kernel.org/linux-cve-announce/2026072538-CVE-2026-64439-5378@gregkh/T
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2026-64439
- ubuntu.com https://ubuntu.com/security/notices/USN-8726-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8726-2
- ubuntu.com https://ubuntu.com/security/notices/USN-8726-3
Show all 19 references
- ubuntu.com https://ubuntu.com/security/notices/USN-8726-4
- ubuntu.com https://ubuntu.com/security/notices/USN-8727-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8728-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8728-2
- ubuntu.com https://ubuntu.com/security/notices/USN-8728-3
- ubuntu.com https://ubuntu.com/security/notices/USN-8760-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8760-2
- ubuntu.com https://ubuntu.com/security/notices/USN-8800-1
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2026-64439
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.