CVE-2026-43366: io_uring/kbuf: check if target buffer list is still legacy on recycle
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by Linux, published 2026-05-08).
Weakness: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (‘Race Condition’)
How it can be exploited
Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 research write-up naming this CVE.
See all 10 references on Exploit Observer
Live scores
- EPSS
- 0.001
low predicted chance of attack - VEDAS
- 0.428
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Linux | from c7fb19428d67 before a7b33671e418 (git commit) from c7fb19428d67 before 439a6728ec46 (git commit) from c7fb19428d67 before f3fb54e7a8b4 (git commit) from c7fb19428d67 before 50ad880db301 (git commit) from c7fb19428d67 before 97b57f69fee1 (git commit) from c7fb19428d67 before c2c185be5c85 (git commit) | Not stated |
| Linux | version 5.19 | 0 is not affected (up to 5.19); 6.1.167 is not affected; 6.6.130 is not affected; 6.12.78 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
References
Other references
- https://git.kernel.org/stable/c/a7b33671e418fca507feebd1d56e7f4952a4b25c
- https://git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570f
- https://git.kernel.org/stable/c/f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa
- https://git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83
- https://git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4
- https://git.kernel.org/stable/c/c2c185be5c85d37215397c8e8781abf0a69bec1f
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
