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). EPSS 0.1% 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-53145 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53145?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53145?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-53145 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 | from 6.18.32 before 6.18.36 |
| Linux | from 7.0.9 before 7.0.13 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.0.13-1 | DEBIAN-CVE-2026-53145 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-53145 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-53145 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-53145 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-53145 |
| Ubuntu | 24.04:LTS | linux-aws-7.0 | 7.0.0-1012.12~24.04.1 | UBUNTU-CVE-2026-53145 USN-8726-1 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-31.31~24.04.1 | UBUNTU-CVE-2026-53145 USN-8726-1 |
| Ubuntu | 24.04:LTS | linux-nvidia-7.0 | 7.0.0-1018.18~24.04.1 | UBUNTU-CVE-2026-53145 USN-8760-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 16 more | no fix listed | UBUNTU-CVE-2026-53145 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-31.31.1~24.04.1 | UBUNTU-CVE-2026-53145 |
| Ubuntu | 26.04:LTS | linux | 7.0.0-31.31 | UBUNTU-CVE-2026-53145 USN-8726-1 |
| Ubuntu | 26.04:LTS | linux-aws | 7.0.0-1012.12 | UBUNTU-CVE-2026-53145 USN-8726-1 |
| Ubuntu | 26.04:LTS | linux-azure | 7.0.0-1014.14 | UBUNTU-CVE-2026-53145 USN-8726-4 |
| 8 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Alpaquita | stream | linux-lts | 6.18.38-r0 | BELL-CVE-2026-53145 |
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 Moderate.
This IMPORTANT impact flaw in the Linux kernel's Direct Rendering Manager (DRM) Graphics Execution Manager (GEM) subsystem affects the kernel and kernel-rt packages in Red Hat Enterprise Linux 7, 8, 9, and 10 and the kernel and kernel-ivos-qualcomm packages in Red Hat In-Vehicle OS 2, while the Red Hat Enterprise Linux 6 Extended Lifecycle Support stream remains under assessment. The flaw is a race condition in the change_handle ioctl, where a concurrent gem_close operation can interfere with the handle replacement performed by gem_change_handle, causing graphics buffer object handles and their references to be managed incorrectly. A local attacker with low privileges could exploit this flaw by racing these ioctl calls to trigger incorrect handling of graphics memory, potentially resulting in memory corruption, system instability, or a denial of service; successful exploitation requires precise timing and has high attack complexity. The upstream fix reworks the handle replacement logic and temporarily disables the change_handle ioctl until the race condition is fully resolved. Red Hat Product Security rates this flaw as IMPORTANT, 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) that matches the upstream CVE.org severity. Remediation is delegated to the kernel maintenance team, and a fix is being pursued for the affected Red Hat products.
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 | Affected | |
| Red Hat Enterprise Linux 6 | kernel | Under investigation | |
| Red Hat Enterprise Linux 7 | kernel | Affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 8 | kernel | Affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 9 | kernel | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | 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-53145.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.