CVE-2026-23259
Use-After-Free Vulnerability in Linux Kernel io_uring Component
Publication date: 2026-03-18
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's io_uring subsystem, specifically in the read/write (rw) path. When a read or write request is processed, if it has an allocated iovec (a structure representing a buffer) attached and the request fails to be put back into the rw_cache, the iovec pointer may not be properly accounted for or freed. This can lead to a potential resource leak or memory management issue. The fix involves modifying the io_rw_recycle() function to indicate whether the request was recycled, which helps determine if the iovec should be freed.
How can this vulnerability impact me? :
This vulnerability can lead to improper memory management in the Linux kernel's io_uring subsystem. Specifically, if iovec pointers are not freed correctly, it may cause memory leaks or resource exhaustion over time. This can degrade system performance or stability, potentially leading to crashes or denial of service conditions if the system runs out of memory or resources.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know