What is CVE-2026-64021?

CVE-2026-64021 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Memory Leak flaw (CWE-401), affecting Linux kernel versions from 6.13 onward and patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64021 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-64021?

CVE-2026-64021 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2026-64021?

Yes, CVE-2026-64021 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 6.13 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-64021 actively exploited?

CVE-2026-64021 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is Memory Leak (CWE-401)?

The product does not release memory after use, causing gradual resource exhaustion. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/401.html

CVE-2026-64021

Medium

In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix exec_queue leak on width check in stream open In xe_oa_stream_open_ioctl(), when param.exec_q->width > 1 the function returns -EOPNOTSUPP directly, skipping the existing err_exec_q cleanup path. The exec_queue reference obtained by xe_exec_queue_lookup() is leaked. The exec queue holds a reference on the xe_file, which is only dropped during queue teardown. The leaked lookup ref is not on the file's exec_queue xarray, so file close cannot release it. This keeps both the exec queue and the file private state pinned indefinitely. Jump to err_exec_q instead of returning directly so the reference is released. (cherry picked from commit 339fa0be9e4a5d69fa47e91f4a36574224fb478f)

Package Linux Kernel

Published 2026-07-19

Last modified 2026-10-13

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-401

CVE-2026-64021 is a Memory Leak vulnerability

What is Memory Leak?

The product does not release memory after use, causing gradual resource exhaustion. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.13 and later are affected. Fixed in 6.18.34, 7.0.11, 7.1 and their respective stable series.

Affected from

≥ 6.13

Fixed in

✓ 6.18.34 6.18.x ✓ 7.0.11 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/04ef7592eaadd9ca8f8f66e76452f73525cff819

Patch
Kernel Git
https://git.kernel.org/stable/c/4b0c4f0c1b133d4bfa31c167200bcda646873328

Patch
Kernel Git
https://git.kernel.org/stable/c/4d25342543c01310fc4e0cba7cb17c775e2421e2

Patch

Details

CVE ID CVE-2026-64021

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-07-19

Modified 2026-10-13

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-64021?

CVE-2026-64021 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Memory Leak flaw (CWE-401) . It affects Linux kernel versions from 6.13 onward and has been patched in 6.18.34, 7.0.11 and 7.1. CVE-2026-64021 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-64021?

CVE-2026-64021 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2026-64021?

Yes. CVE-2026-64021 has been patched. Fixed versions include 6.18.34, 7.0.11 and 7.1. If you are running Linux kernel 6.13 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-64021 actively exploited?

No. CVE-2026-64021 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.