CVE-2026-64439: crypto: krb5 - filter out async aead implementations at alloc
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.63% (FIRST EPSS); higher than 50.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2b7bd6dccff14b8b632c5244f1fd506918077221, 6c9dddeb582fde005360f4fe02c760d45ca05fb5, ef6feb77e2d91761427c5b773edc9c97e1b706ad.
Low priority for now. Upgrade to Linux Linux 2b7bd6dccff14b8b632c5244f1fd506918077221, 6c9dddeb582fde005360f4fe02c760d45ca05fb5, ef6feb77e2d91761427c5b773edc9c97e1b706ad or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Oct 24, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- CWE-416
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.15 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.15affected
- 00244da40f7821b242c4612428d4192230dba27f and later · before ef6feb77e2d91761427c5b773edc9c97e1b706adaffected · git
- 00244da40f7821b242c4612428d4192230dba27f and later · before 2b7bd6dccff14b8b632c5244f1fd506918077221affected · git
- 00244da40f7821b242c4612428d4192230dba27f and later · before 6c9dddeb582fde005360f4fe02c760d45ca05fb5affected · git
- before 6.15not affected · semver
- 6.18.39 and later · up to and including 6.18.*not affected · semver
- 7.1.4 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
| Red Hat:rhel_e4s:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.136.1.el9_4 | 0:7.3.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-devel | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-doc | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
| Red Hat:rhel_e4s:9.4::appstream | kernel-zfcpdump-devel | before 0:5.14.0-427.136.1.el9_4 | 0:5.14.0-427.136.1.el9_4 |
+53
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64436Jul 25, 2026 · net: af_key: initialize alg_key_len for IPComp states28Monitor
- ← EarlierCVE-2026-64438Jul 25, 2026 · crypto: qat - fix VF2PF work teardown race in adf_disable_sriov()35Monitor
- Later →CVE-2026-64440Jul 25, 2026 · staging: rtl8723bs: fix OOB write in HT_caps_handler()32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2b7bd6dccff14b8b632c5244f1fd506918077221 | Vendor (CNA) |
| Linux Linux | 6c9dddeb582fde005360f4fe02c760d45ca05fb5 | Vendor (CNA) |
| Linux Linux | ef6feb77e2d91761427c5b773edc9c97e1b706ad | Vendor (CNA) |
| debian:linux | 7.1.4-1 · Debian:14 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.136.1.el9_4 · Red Hat:rhel_e4s:9.4::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.