CVE-2026-64599

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-06. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

crypto: amlogic - avoid double cleanup in meson_crypto_probe()

When meson_allocate_chanlist() fails after a partial allocation, it already unwinds the allocated chanlist state through its local error path. meson_crypto_probe() then jump to error_flow and calls meson_free_chanlist() again, causing the same per-flow resources to be torn down twice. In the reproduced failure path, the second teardown re-entered crypto_engine_exit() on an already destroyed worker and KASAN reported a slab-use-after-free in kthread_destroy_worker().

Prevent double-free by handling partial allocation failures locally within meson_allocate_chanlist() and skipping the outer cleanup path.

The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available.

The bug was reproduced in a QEMU x86_64 guest booted with KASAN on v7.1, using the reproducer under tools/testing/meson_crypto_probe. The reproducer forces the second dma_alloc_attrs() call in the gxl-crypto probe path to return NULL, making meson_allocate_chanlist() fail after partial initialization. On the unpatched kernel this reliably triggered a slab-use-after-free. With this fix applied, the same reproducer no longer emits any KASAN report and the probe fails cleanly with -ENOMEM.

================================================================== BUG: KASAN: slab-use-after-free in kthread_destroy_worker+0xb2/0xd0 Read of size 8 at addr ff1100010c057a68 by task insmod/265

CPU: 1 UID: 0 PID: 265 Comm: insmod Tainted: G O 7.1.0-rc2-00376-g810af9adc907-dirty #10 PREEMPT(lazy) Tainted: [O]=OOT_MODULE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x68/0xa0 print_report+0xcb/0x5e0 ? __virt_addr_valid+0x21d/0x3f0 ? kthread_destroy_worker+0xb2/0xd0 ? kthread_destroy_worker+0xb2/0xd0 kasan_report+0xca/0x100 ? kthread_destroy_worker+0xb2/0xd0 kthread_destroy_worker+0xb2/0xd0 meson_crypto_probe+0x4d0/0xc10 [amlogic_gxl_crypto] platform_probe+0x99/0x140 really_probe+0x1c6/0x6a0 ? __pfx___device_attach_driver+0x10/0x10 __driver_probe_device+0x248/0x310 ? acpi_driver_match_device+0xb0/0x100 driver_probe_device+0x48/0x210 ? __pfx___device_attach_driver+0x10/0x10 __device_attach_driver+0x160/0x320 bus_for_each_drv+0x104/0x190 ? __pfx_bus_for_each_drv+0x10/0x10 ? _raw_spin_unlock_irqrestore+0x2c/0x50 __device_attach+0x19d/0x3b0 ? __pfx___device_attach+0x10/0x10 ? do_raw_spin_unlock+0x53/0x220 device_initial_probe+0x78/0xa0 bus_probe_device+0x5b/0x130 device_add+0xcfd/0x1430 ? __pfx_device_add+0x10/0x10 ? insert_resource+0x34/0x50 ? lock_release+0xc9/0x290 platform_device_add+0x24e/0x590 ? __pfx_meson_crypto_probe_repro_init+0x10/0x10 [meson_crypto_probe_repro] meson_crypto_probe_repro_init+0x330/0xff0 [meson_crypto_probe_repro] do_one_initcall+0xc0/0x450 ? __pfx_do_one_initcall+0x10/0x10 ? _raw_spin_unlock_irqrestore+0x2c/0x50 ? __create_object+0x59/0x80 ? kasan_unpoison+0x27/0x60 do_init_module+0x27b/0x7d0 ? __pfx_do_init_module+0x10/0x10 ? kasan_quarantine_put+0x84/0x1d0 ? kfree+0x32c/0x510 ? load_module+0x561e/0x5ff0 load_module+0x54fe/0x5ff0 ? __pfx_load_module+0x10/0x10 ? security_file_permission+0x20/0x40 ? kernel_read_file+0x23d/0x6e0 ? mmap_region+0x235/0x4a0 ? __pfx_kernel_read_file+0x10/0x10 ? __file_has_perm+0x2c0/0x3e0 init_module_from_file+0x158/0x180 ? __pfx_init_module_from_file+0x10/0x10 ? __lock_acquire+0x45a/0x1ba0 ? idempotent_init_module+0x315/0x610 ? lock_release+0xc9/0x290 ? lock ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 6, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Aug 8, 2026
Patch available.
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f30e2b879bda14bc3e1524fba6f8ab9ec119da90
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c80360b4e85099fc3835378a96a59c0a2480fb07
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2c48aa7a6be36d4c93da75d14d4b4f2f4168c81
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84a00be9b736aa5dce902a290f62cbbbdcfab9ed
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6effdbaca3cd8354540bdf42c7f5fb84412afeb7
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dda8406d8a3da2519c8b388d443d7357839cb63
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d827ade51a24e18d81afb9f32756d339520a14c
Web page

crypto: amlogic - avoid double cleanup in meson_crypto_probe() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5b452019a4127f63c1f2147237fc287d1581f606

Vendor Advisories for CVE-2026-64599(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-31.31~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-19ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-19ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)
  • every version up to 5.10.262-1: fixed in 5.10.262-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)
  • every version up to 6.12.96-1: fixed in 6.12.96-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (159 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(20)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 93× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 290 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 190 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 21:42 UTCEG score recompute
  2. 2026-10-19 21:42 UTCVendor advisory
  3. 2026-10-19 21:42 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-19 20:54 UTCEG score recompute
  5. 2026-10-19 20:54 UTCVendor advisory
  6. 2026-10-19 20:54 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-18 03:22 UTCEG score recompute
  10. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-16 17:35 UTCEG score recompute
  12. 2026-10-16 17:35 UTCVendor advisory
  13. 2026-10-16 17:35 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-16 16:09 UTCEG score recompute
  15. 2026-10-16 16:09 UTCVendor advisory
  16. 2026-10-16 16:09 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-13 11:38 UTCEG score recompute
  21. 2026-10-13 11:38 UTCVendor advisory
  22. 2026-10-13 11:38 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-12 15:47 UTCEG score recompute
  25. 2026-10-11 19:32 UTCEG score recompute
Show 75 more
  1. 2026-10-11 16:47 UTCEG score recompute
  2. 2026-10-11 14:08 UTCEG score recompute
  3. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-06 23:34 UTCEG score recompute
  9. 2026-10-06 23:34 UTCVendor advisory
  10. 2026-10-06 23:33 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-05 19:31 UTCEG score recompute
  13. 2026-10-05 19:31 UTCVendor advisory
  14. 2026-10-05 19:30 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-04 23:28 UTCEG score recompute
  17. 2026-10-04 23:28 UTCVendor advisory
  18. 2026-10-04 23:28 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-04 05:55 UTCEG score recompute
  21. 2026-10-04 05:55 UTCVendor advisory
  22. 2026-10-04 05:55 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-03 01:06 UTCEG score recompute
  25. 2026-10-03 01:06 UTCVendor advisory
  26. 2026-10-03 01:06 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  27. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-10-02 09:48 UTCEG score recompute
  29. 2026-10-02 09:48 UTCVendor advisory
  30. 2026-10-02 09:48 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-10-01 14:31 UTCVendor advisory
  33. 2026-10-01 14:30 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-10-01 01:49 UTCEG score recompute
  35. 2026-10-01 01:49 UTCVendor advisory
  36. 2026-10-01 01:49 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-09-29 06:03 UTCEG score recompute
  39. 2026-09-29 06:03 UTCVendor advisory
  40. 2026-09-29 06:03 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  42. 2026-09-28 06:17 UTCVendor advisory
  43. 2026-09-28 06:17 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-09-27 17:36 UTCEG score recompute
  45. 2026-09-27 17:36 UTCVendor advisory
  46. 2026-09-27 17:36 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-09-25 04:27 UTCEG score recompute
  49. 2026-09-25 04:27 UTCVendor advisory
  50. 2026-09-25 04:27 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-09-24 05:41 UTCEG score recompute
  52. 2026-09-24 05:41 UTCVendor advisory
  53. 2026-09-24 05:41 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  55. 2026-09-23 16:30 UTCVendor advisory
  56. 2026-09-23 16:30 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-23 03:41 UTCEG score recompute
  58. 2026-09-23 03:41 UTCVendor advisory
  59. 2026-09-23 03:41 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-09-22 15:00 UTCVendor advisory
  61. 2026-09-22 14:59 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-22 01:42 UTCEG score recompute
  63. 2026-09-22 01:42 UTCVendor advisory
  64. 2026-09-22 01:42 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-21 12:59 UTCVendor advisory
  66. 2026-09-21 12:59 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-20 10:59 UTCVendor advisory
  68. 2026-09-20 10:59 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-09-19 21:38 UTCEG score recompute
  70. 2026-09-19 21:38 UTCVendor advisory
  71. 2026-09-19 21:38 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-09-19 07:32 UTCEG score recompute
  73. 2026-09-19 07:32 UTCVendor advisory
  74. 2026-09-19 07:32 UTCGHSA enrichmentGHSA-j4fc-xrx5-phgr · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64599?
CVE-2026-64599 is a high-severity vulnerability; its CVE record was published on August 6, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: amlogic - avoid double cleanup in mesoncryptoprobe() When mesonallocatechanlist() fails after a partial allocation, it already unwinds the allocated chanlist state through its local error path. mesoncryptoprobe() then jump…
When was the CVE record for CVE-2026-64599 published?
The CVE record for CVE-2026-64599 was published on August 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-64599 actively exploited?
CVE-2026-64599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64599?
CVE-2026-64599 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64599?
A fix for CVE-2026-64599 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64599 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64599

Explore →

Is Your Infrastructure Affected by CVE-2026-64599?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs