CVE-2026-43366: high-severity vulnerability in Linux
io_uring/kbuf: check if target buffer list is still legacy on recycle
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.8epss 0.1%
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
Linux · LinuxRelated CVEs — Linux
In the same product, most dangerous first.
CVE-2026-31431HIGHcrypto: algif_aead - Revert to operating out-of-placeEPSS 98.1%KEVCVE-2026-46300HIGHnet: skbuff: preserve shared-frag marker during coalescingEPSS 17.2%KEVCVE-2024-53197HIGHALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devicesEPSS 4.1%KEVCVE-2024-53104HIGHmedia: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_formatEPSS 3.4%KEVCVE-2025-39682CRITICALtls: fix handling of zero-length records on the rx_listEPSS 3.3%KEVCVE-2024-36971HIGHnet: fix __dst_negative_advice() raceEPSS 2.7%KEV
References
https://git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570fhttps://git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83https://git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4https://git.kernel.org/stable/c/a7b33671e418fca507feebd1d56e7f4952a4b25chttps://git.kernel.org/stable/c/c2c185be5c85d37215397c8e8781abf0a69bec1fhttps://git.kernel.org/stable/c/f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa