RHSA-2026:93453: Moderate: libkcapi security update
libkcapi allows user-space to access the Linux kernel crypto API. This library uses the netlink interface and exports easy to use APIs so that a developer does not need to consider the low-level netlink interface handling. The library does not implement any cipher algorithms. All consumer requests are sent to the kernel for processing. Results from the kernel crypto API are returned to the consumer via the library API. The kernel interface and therefore this library can be used by unprivileged processes.Security Fix(es): libkcapi: Memory corruption via uncanceled AIO requests on error in libkcapi's one-shot AIO path (CVE-2026-71226) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/libkcapito a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1 - Upgrade
Upgrade
redhat/libkcapi-debuginfoto a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1 - Upgrade
Upgrade
redhat/libkcapi-debugsourceto a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1 - Upgrade
Upgrade
redhat/libkcapi-hmaccalcto a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1 - Upgrade
Upgrade
redhat/libkcapi-hmaccalc-debuginfoto a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1 - Upgrade
Upgrade
redhat/libkcapi-tests-debuginfoto a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1 - Upgrade
Upgrade
redhat/libkcapi-tools-debuginfoto a version that resolves this vulnerability.Fixed in 1.2.0-3.el8_8.1
Event History
Frequently Asked Questions
Which systems and applications are exposed to this issue?
Systems are exposed where applications use libkcapi, particularly its one-shot asynchronous I/O path. Because the kernel crypto API and libkcapi can be used by unprivileged processes, affected consumers do not necessarily need elevated privileges to use the interface.
What condition is required to trigger the memory corruption?
The issue occurs when uncanceled AIO requests remain after an error in libkcapi's one-shot AIO path. The provided information does not identify a specific application workload or configuration required beyond use of that affected path.
How can I determine whether this advisory applies to my environment?
Identify applications that link to or otherwise use libkcapi and determine whether they use its one-shot AIO functionality. The advisory identifies CVE-2026-71226 as the relevant issue.