In the Linux kernel, the following vulnerability has been resolved: crypto: amlogic - avoid double cleanup in meson_crypto_probe() When… (CVE-2026-64599)
A use-after-free vulnerability in the Linux kernel's amlogic crypto driver (meson_crypto_probe) was identified and resolved. The issue occurs due to a double cleanup of resources when meson_allocate_chanlist() fails after partial allocation, leading to a slab-use-after-free detected by KASAN. This flaw could cause kernel memory corruption during device probing. The vulnerability was fixed by adjusting error handling to prevent double freeing of resources. No evidence of exploitation in the wild is reported.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's amlogic crypto driver arises from double cleanup in meson_crypto_probe(). When meson_allocate_chanlist() fails after partially allocating resources, it unwinds the allocated state locally. However, meson_crypto_probe() also attempts to free the same resources again, causing a double free and subsequent use-after-free in kthread_destroy_worker(), as detected by KASAN. The fix involves handling partial allocation failures entirely within meson_allocate_chanlist() to avoid the outer cleanup path and prevent double freeing. The issue was reproducible on kernel version 7.1-rc2 with KASAN enabled and is now resolved.
Potential Impact
The vulnerability leads to a kernel slab-use-after-free condition during device probing, which can cause kernel memory corruption and potential instability or crashes. There is no indication of remote code execution or privilege escalation from the provided data. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been applied to the Linux kernel to prevent the double cleanup and use-after-free. Users should update to a kernel version that includes this fix. Since this is a kernel-level bug, applying the official kernel patch or upgrading to a fixed kernel release is the recommended remediation. Patch status is not explicitly stated but the description confirms the bug has been resolved in the kernel source. Check the Linux kernel vendor advisory or mainline kernel releases for the official fixed version.
In the Linux kernel, the following vulnerability has been resolved: crypto: amlogic - avoid double cleanup in meson_crypto_probe() When… (CVE-2026-64599)
Description
A use-after-free vulnerability in the Linux kernel's amlogic crypto driver (meson_crypto_probe) was identified and resolved. The issue occurs due to a double cleanup of resources when meson_allocate_chanlist() fails after partial allocation, leading to a slab-use-after-free detected by KASAN. This flaw could cause kernel memory corruption during device probing. The vulnerability was fixed by adjusting error handling to prevent double freeing of resources. No evidence of exploitation in the wild is reported.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's amlogic crypto driver arises from double cleanup in meson_crypto_probe(). When meson_allocate_chanlist() fails after partially allocating resources, it unwinds the allocated state locally. However, meson_crypto_probe() also attempts to free the same resources again, causing a double free and subsequent use-after-free in kthread_destroy_worker(), as detected by KASAN. The fix involves handling partial allocation failures entirely within meson_allocate_chanlist() to avoid the outer cleanup path and prevent double freeing. The issue was reproducible on kernel version 7.1-rc2 with KASAN enabled and is now resolved.
Potential Impact
The vulnerability leads to a kernel slab-use-after-free condition during device probing, which can cause kernel memory corruption and potential instability or crashes. There is no indication of remote code execution or privilege escalation from the provided data. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been applied to the Linux kernel to prevent the double cleanup and use-after-free. Users should update to a kernel version that includes this fix. Since this is a kernel-level bug, applying the official kernel patch or upgrading to a fixed kernel release is the recommended remediation. Patch status is not explicitly stated but the description confirms the bug has been resolved in the kernel source. Check the Linux kernel vendor advisory or mainline kernel releases for the official fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-j4fc-xrx5-phgr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64599"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a74cfa0bf8831d5391b0764
Added to database: 08/06/2026, 18:17:04 UTC
Last enriched: 08/06/2026, 19:11:30 UTC
Last updated: 08/07/2026, 00:41:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.