CVE-2026-23421
Memory Leak in Linux Kernel drm/xe Configfs Component Fixed
Publication date: 2026-04-03
Last updated on: 2026-04-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.18 |
| linux | linux_kernel | From 6.18.1 (inc) to 6.18.17 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.7 (exc) |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix for the drm/xe/configfs memory leak issue. This fix ensures that the ctx_restore_mid_bb memory is properly freed when the configfs device is removed, preventing memory leaks.
If updating immediately is not possible, avoid removing the configfs device related to drm/xe until a patch is applied, as the vulnerability occurs during device release.
Can you explain this vulnerability to me?
This vulnerability is related to the Linux kernel's drm/xe/configfs component. Specifically, it involves improper memory management where a certain allocated memory (ctx_restore_mid_bb) is not freed properly when the configfs device is removed. The function wa_bb_store() allocates this memory, but the release function xe_config_device_release() only frees a different memory allocation (ctx_restore_post_bb), leading to a memory leak.
How can this vulnerability impact me? :
The impact of this vulnerability is a memory leak in the Linux kernel's drm/xe/configfs subsystem. Over time, this could lead to increased memory usage and potentially degrade system performance or stability, especially on systems that frequently add and remove configfs devices.