CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-64008 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64008?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64008?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64008 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.18 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.18 | 6.18.35 |
| Linux | 7.0 | 7.0.12 |
| Linux | later releases | 7.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.0.12-1 | DEBIAN-CVE-2026-64008 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-64008 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-64008 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-64008 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-64008 |
| Ubuntu | 24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-64008 USN-8728-2 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-64008 |
| Ubuntu | 24.04:LTS | linux-gcp-7.0, linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64008 USN-8728-1 USN-8728-3 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-64008 |
| Ubuntu | 24.04:LTS | linux-nvidia-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-64008 USN-8663-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 18 more | no fix listed | UBUNTU-CVE-2026-64008 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-28.28.1~24.04.3 | UBUNTU-CVE-2026-64008 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-28.28 | UBUNTU-CVE-2026-64008 |
| 9 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | stream | linux-lts | 6.18.35-r1 | BELL-CVE-2026-64008 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Important.
This Important-severity use-after-free flaw in the Linux kernel accel/rocket driver does not affect Red Hat Enterprise Linux or Red Hat In-Vehicle OS, because the vulnerable code is not present in the shipped kernel packages. The flaw is in rocket_ioctl_create_bo(), which inserts a Graphics Execution Manager (GEM) handle into the file's IDR via drm_gem_handle_create() before several fallible operations (scatter-gather table allocation, drm_mm node insertion, and IOMMU mapping) have completed. If any of those operations fail, the error path frees the GEM object without removing the handle from the IDR, leaving a dangling handle that points to freed slab memory. A local attacker with access to the rocket DRM accelerator device could then issue a subsequent ioctl (PREP_BO, FINI_BO, or SUBMIT) using the dangling handle, causing drm_gem_object_lookup() to return and dereference the freed memory. This could result in a kernel use-after-free that crashes the system (kernel panic) or potentially leads to privilege escalation. Red Hat rates this flaw with a CVSS 3.1 score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), which is lower than the upstream CVE record score of 7.8, because successful exploitation requires a local attacker to reliably trigger specific allocation failures in the buffer-object creation path.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Not affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-64008.