Kernel memory reuse via double channel cleanup
Published Aug 6, 2026 · Updated Aug 6, 2026
Use-after-free in the Linux Amlogic GXL crypto driver allows local users to access freed kernel memory during device probing. After meson_allocate_chanlist() unwinds a partial allocation, meson_crypto_probe() calls meson_free_chanlist() and destroys the same per-flow worker again. The published reproducer requires privileged module loading and an injected allocation failure; the demonstrated result is a KASAN-detected slab use-after-free.
Summary
What happened
Use-after-free in the Linux Amlogic GXL crypto driver allows local users to access freed kernel memory during device probing. After meson_allocate_chanlist() unwinds a partial allocation, meson_crypto_probe() calls meson_free_chanlist() and destroys the same per-flow worker again. The published reproducer requires privileged module loading and an injected allocation failure; the demonstrated result is a KASAN-detected slab use-after-free.
The record
- CVE
- CVE-2026-64599
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <5b452019a4127f63c1f2147237fc287d1581f606
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <6d827ade51a24e18d81afb9f32756d339520a14c
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <6dda8406d8a3da2519c8b388d443d7357839cb63
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <6effdbaca3cd8354540bdf42c7f5fb84412afeb7
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <84a00be9b736aa5dce902a290f62cbbbdcfab9ed
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <c2c48aa7a6be36d4c93da75d14d4b4f2f4168c81
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <c80360b4e85099fc3835378a96a59c0a2480fb07
- Affected versionversion=48fe583fe54177bfb80f348e2a5cc34c3f710095 <f30e2b879bda14bc3e1524fba6f8ab9ec119da90
- Affected versionversion=5.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo