In the Linux kernel, the following vulnerability has been resolved:
io_uring/kbuf: check if target buffer list is still legacy on recycle
There's a gap between when the buffer was grabbed and when it
potentially gets recycled, where if the list is empty, someone could've
upgraded it to a ring provided type. This can happen if the request
is forced via io-wq. The legacy recycling is missing checking if the
buffer_list still exists, and if it's of the correct type. Add those
checks.
References
Configurations
Configuration 1 (hide)
|
History
11 Nov 2026, 20:10
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
19 Oct 2026, 20:18
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-362 |
Information
Published : 2026-05-08 15:16
Updated : 2026-11-11 20:10
NVD link : CVE-2026-43366
Mitre link : CVE-2026-43366
CVE.ORG link : CVE-2026-43366
JSON object : View
Products Affected
linux
- linux_kernel
CWE
NVD-CWE-noinfo
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
