8 matches found
libkcapi: Memory corruption via uncanceled AIO requests on error in libkcapi's one-shot AIO path
Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers...
libkcapi: Memory corruption via uncanceled AIO requests on error in libkcapi's one-shot AIO path
Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers...
libkcapi: Memory corruption via uncanceled AIO requests on error in libkcapi's one-shot AIO path
Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers...
Libkcapi: memory corruption via uncanceled aio requests on error in libkcapi's one-shot aio path
...
CVE-2026-71226
Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers...
CVE-2026-71226 Libkcapi: memory corruption via uncanceled aio requests on error in libkcapi's one-shot aio path
Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers...
CVE-2026-71226
CVE-2026-71226 affects libkcapi’s one-shot AIO path. The root cause is memory corruption when an uncanceled AIO request returns an error before all submitted IOCBs are drained, allowing later writes from the kernel into caller-owned output buffers. The available sources describe the vulnerability...
EUVD-2026-53375
Memory Corruption via Uncanceled AIO Requests on Error: libkcapi's one-shot AIO path can return an error before all submitted IOCBs are drained, allowing later kernel writes into caller-owned output buffers...