Description
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.
Affected products
linux: linux kernel
References6
- git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570f Patch
- git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83 Patch
- git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4 Patch
- git.kernel.org/stable/c/a7b33671e418fca507feebd1d56e7f4952a4b25c Patch
- git.kernel.org/stable/c/c2c185be5c85d37215397c8e8781abf0a69bec1f Patch
- git.kernel.org/stable/c/f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa Patch
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 2 · as of 13 November 2026
- CWE
- CWE-362
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.