CVEvulnerability
CVE-2026-43366
7.8 HIGH
Official page ↗
- Status
- Modified
- Published
- 2026-05-08
- Last modified
- 2026-10-19
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-362
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 configurations
• linux linux kernel (>= 5.19 < 6.1.167)
• linux linux kernel (>= 6.2 < 6.6.130)
• linux linux kernel (>= 6.7 < 6.12.78)
• linux linux kernel (>= 6.13 < 6.18.19)
• linux linux kernel (>= 6.19 < 6.19.9)
• linux linux kernel 7.0
Related
Weakness · CWE (1)
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness
References
- 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