Bug 2468231 (CVE-2026-43366) - CVE-2026-43366 kernel: io_uring/kbuf: check if target buffer list is still legacy on recycle
Summary: CVE-2026-43366 kernel: io_uring/kbuf: check if target buffer list is still le...
Keywords:
Status: NEW
Alias: CVE-2026-43366
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-08 15:06 UTC by OSIDB Bzimport
Modified: 2026-05-08 20:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-08 15:06:02 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.