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.
Fix
Patch, vendor advisory and mitigation references on NVD 6
- https://git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570f Patch
- https://git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83 Patch
- https://git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4 Patch
- https://git.kernel.org/stable/c/a7b33671e418fca507feebd1d56e7f4952a4b25c Patch
- https://git.kernel.org/stable/c/c2c185be5c85d37215397c8e8781abf0a69bec1f Patch
- https://git.kernel.org/stable/c/f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- CwesCWE-362NVD modified 2026-10-19 20:18
- StatusAnalyzed → ModifiedNVD modified 2026-10-19 20:18
- First seenCVSS 7.8 · linuxNVD modified 2026-10-16 16:17
Affected (CPE criteria) 4
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
References 6
- https://git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570f Patch
- https://git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83 Patch
- https://git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4 Patch
- https://git.kernel.org/stable/c/a7b33671e418fca507feebd1d56e7f4952a4b25c Patch
- https://git.kernel.org/stable/c/c2c185be5c85d37215397c8e8781abf0a69bec1f Patch
- https://git.kernel.org/stable/c/f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa Patch