What is CVE-2026-46224?

CVE-2026-46224 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.18 onward and patched in 6.18.32, 7.0.9 and 7.1. CVE-2026-46224 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

CVE-2026-46224 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-46224?

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

Is CVE-2026-46224 actively exploited?

CVE-2026-46224 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-46224

Medium

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure When drm_gpuvm_resv_object_alloc() fails, the pre-allocated storage bo is not freed. Add xe_bo_free(storage) before returning the error. xe_dma_buf_init_obj() calls xe_bo_init_locked(), which frees the bo on error. Therefore, xe_dma_buf_init_obj() must also free the bo on its own error paths. Otherwise, since xe_gem_prime_import() cannot distinguish whether the failure originated from xe_dma_buf_init_obj() or from xe_bo_init_locked(), it cannot safely decide whether the bo should be freed. Add comments documenting the ownership semantics: on success, ownership of storage is transferred to the returned drm_gem_object; on failure, storage is freed before returning. v2: Add comments to explain the free logic. (cherry picked from commit 78a6c5f899f22338bbf48b44fb8950409c5a69b9)

Package Linux Kernel

Published 2026-05-28

Last modified 2026-06-10

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-46224 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.18 and later are affected. Fixed in 6.18.32, 7.0.9, 7.1 and their respective stable series.

Affected from

≥ 6.18

Fixed in

✓ 6.18.32 6.18.x ✓ 7.0.9 7.0.x ✓ 7.1

References

3 total

Kernel Git
https://git.kernel.org/stable/c/8fa8c2a22585fcb31dc605b91a67bbcca223fdd7

Patch
Kernel Git
https://git.kernel.org/stable/c/93a528f67ce5095bcab46a69839eca97f43dd352

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

Patch

Details

CVE ID CVE-2026-46224

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-05-28

Modified 2026-06-10

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-46224?

CVE-2026-46224 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.18 onward and has been patched in 6.18.32, 7.0.9 and 7.1. CVE-2026-46224 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-46224?

CVE-2026-46224 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-46224?

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

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