CVE-2026-43224
Awaiting Analysis Awaiting Analysis - Queue
io_uring zcrx sgtable leak in Linux kernel

Publication date: 2026-05-06

Last updated on: 2026-05-06

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix sgtable leak on mapping failures In an unlikely case when io_populate_area_dma() fails, which could only happen on a PAGE_POOL_32BIT_ARCH_WITH_64BIT_DMA machine, io_zcrx_map_area() will have an initialised and not freed table. It was supposed to be cleaned up in the error path, but !is_mapped prevents that.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-06
Generated
2026-05-06
AI Q&A
2026-05-06
EPSS Evaluated
N/A
NVD
CVE-2026-43224
EUVD
EUVD-2026-27785
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

The impact of this vulnerability is a resource leak in the Linux kernel's io_uring subsystem. Specifically, memory allocated for the scatter-gather table may not be freed properly on certain hardware architectures when an error occurs. Over time, this could lead to increased memory usage and potential system instability or degraded performance.


Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's io_uring subsystem, specifically in the io_zcrx_map_area() function. When the function io_populate_area_dma() fails on certain machines (PAGE_POOL_32BIT_ARCH_WITH_64BIT_DMA), a scatter-gather table (sgtable) is initialized but not properly freed due to a logic condition (!is_mapped) that prevents cleanup in the error path. This results in a resource leak.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart