{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64599 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64599 is a high-severity use after free vulnerability in Linux, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64599 and fix it if it is affected.\n\nWhat it is: CVE-2026-64599 is a high-severity use after free vulnerability in Linux, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64599 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-64599/ (Markdown: https://insights.sbomify.com/CVE-2026-64599/index.md)","id":"CVE-2026-64599","markdown":"https://insights.sbomify.com/CVE-2026-64599/index.md","name":"CVE-2026-64599","record":{"aliases":["BELL-CVE-2026-64599","DEBIAN-CVE-2026-64599","GHSA-j4fc-xrx5-phgr","UBUNTU-CVE-2026-64599"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel crypto driver","requires_auth":"low_privilege","summary":"A double-free vulnerability in the Amlogic crypto driver allows attackers to trigger a use-after-free, potentially causing system crashes or arbitrary code execution.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: amlogic - avoid double cleanup in meson_crypto_probe()\n\nWhen meson_allocate_chanlist() fails after a partial allocation, it already\nunwinds the allocated chanlist state through its local error path.\nmeson_crypto_probe() then jump to error_flow and calls\nmeson_free_chanlist() again, causing the same per-flow resources to be torn\ndown twice. In the reproduced failure path, the second teardown\nre-entered crypto_engine_exit() on an already destroyed worker and KASAN\nreported a slab-use-after-free in kthread_destroy_worker().\n\nPrevent double-free by handling partial allocation failures locally within\nmeson_allocate_chanlist() and skipping the outer cleanup path.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing\nv6.13-rc1. The tool is still under development and is not yet publicly\navailable.\n\nThe bug was reproduced in a QEMU x86_64 guest booted with KASAN on v7.1,\nusing the reproducer under tools/testing/meson_crypto_probe. The reproducer\nforces the second dma_alloc_attrs() call in the gxl-crypto probe path to\nreturn NULL, making meson_allocate_chanlist() fail after partial\ninitialization. On the unpatched kernel this reliably triggered a\nslab-use-after-free. With this fix applied, the same reproducer no longer\nemits any KASAN report and the probe fails cleanly with -ENOMEM.\n\n    ==================================================================\n    BUG: KASAN: slab-use-after-free in kthread_destroy_worker+0xb2/0xd0\n    Read of size 8 at addr ff1100010c057a68 by task insmod/265\n\n    CPU: 1 UID: 0 PID: 265 Comm: insmod Tainted: G           O        7.1.0-rc2-00376-g810af9adc907-dirty #10 PREEMPT(lazy)\n    Tainted: [O]=OOT_MODULE\n    Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x68/0xa0\n     print_report+0xcb/0x5e0\n     ? __virt_addr_valid+0x21d/0x3f0\n     ? kthread_destroy_worker+0xb2/0xd0\n     ? kthread_destroy_worker+0xb2/0xd0\n     kasan_report+0xca/0x100\n     ? kthread_destroy_worker+0xb2/0xd0\n     kthread_destroy_worker+0xb2/0xd0\n     meson_crypto_probe+0x4d0/0xc10 [amlogic_gxl_crypto]\n     platform_probe+0x99/0x140\n     really_probe+0x1c6/0x6a0\n     ? __pfx___device_attach_driver+0x10/0x10\n     __driver_probe_device+0x248/0x310\n     ? acpi_driver_match_device+0xb0/0x100\n     driver_probe_device+0x48/0x210\n     ? __pfx___device_attach_driver+0x10/0x10\n     __device_attach_driver+0x160/0x320\n     bus_for_each_drv+0x104/0x190\n     ? __pfx_bus_for_each_drv+0x10/0x10\n     ? _raw_spin_unlock_irqrestore+0x2c/0x50\n     __device_attach+0x19d/0x3b0\n     ? __pfx___device_attach+0x10/0x10\n     ? do_raw_spin_unlock+0x53/0x220\n     device_initial_probe+0x78/0xa0\n     bus_probe_device+0x5b/0x130\n     device_add+0xcfd/0x1430\n     ? __pfx_device_add+0x10/0x10\n     ? insert_resource+0x34/0x50\n     ? lock_release+0xc9/0x290\n     platform_device_add+0x24e/0x590\n     ? __pfx_meson_crypto_probe_repro_init+0x10/0x10 [meson_crypto_probe_repro]\n     meson_crypto_probe_repro_init+0x330/0xff0 [meson_crypto_probe_repro]\n     do_one_initcall+0xc0/0x450\n     ? __pfx_do_one_initcall+0x10/0x10\n     ? _raw_spin_unlock_irqrestore+0x2c/0x50\n     ? __create_object+0x59/0x80\n     ? kasan_unpoison+0x27/0x60\n     do_init_module+0x27b/0x7d0\n     ? __pfx_do_init_module+0x10/0x10\n     ? kasan_quarantine_put+0x84/0x1d0\n     ? kfree+0x32c/0x510\n     ? load_module+0x561e/0x5ff0\n     load_module+0x54fe/0x5ff0\n     ? __pfx_load_module+0x10/0x10\n     ? security_file_permission+0x20/0x40\n     ? kernel_read_file+0x23d/0x6e0\n     ? mmap_region+0x235/0x4a0\n     ? __pfx_kernel_read_file+0x10/0x10\n     ? __file_has_perm+0x2c0/0x3e0\n     init_module_from_file+0x158/0x180\n     ? __pfx_init_module_from_file+0x10/0x10\n     ? __lock_acquire+0x45a/0x1ba0\n     ? idempotent_init_module+0x315/0x610\n     ? lock_release+0xc9/0x290\n     ? lock\n---truncated---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"crypto: amlogic - avoid double cleanup in meson_crypto_probe()","id":"CVE-2026-64599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"xfs: resample the data fork mapping after cycling ILOCK","id":"CVE-2026-64600"},"packages":[],"prev":{"headline":"smb/client: Fix error code in smb2_aead_req_alloc()","id":"CVE-2026-64598"},"products":["Linux"],"published":"2026-08-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A double-free vulnerability in the Amlogic crypto driver allows attackers to trigger a use-after-free, potentially causing system crashes or arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2026-64599/"}