CVE-2026-71227
Received Received - Intake

Denial of Service in libkcapi via AIO Handle Reuse

Vulnerability report for CVE-2026-71227, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-05

Last updated on: 2026-08-05

Assigner: Red Hat, Inc.

Description

A flaw was found in libkcapi. A local attacker can influence an application that uses the Asynchronous Input/Output (AIO) interface. By reusing an AIO-enabled handle after a prior completion error, the _kcapi_aio_read_all() function can enter a non-terminating wait loop. This can lead to a persistent denial of service, making the affected application or thread unresponsive.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-05
Last Modified
2026-08-05
Generated
2026-08-05
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-835 The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a flaw in libkcapi where a local attacker can exploit the Asynchronous Input/Output (AIO) interface. By reusing an AIO-enabled handle after a prior completion error, the _kcapi_aio_read_all() function may enter an infinite wait loop, causing a persistent denial of service. This makes the affected application or thread unresponsive.

Detection Guidance

Detecting this vulnerability requires checking for applications using libkcapi with AIO enabled. Monitor for unresponsive threads or high CPU usage in processes linked to libkcapi. Check logs for repeated AIO completion errors or infinite loops in _kcapi_aio_read_all().

Commands to check for affected applications: lsof | grep libkcapi, ps aux | grep -E 'libkcapi|AIO', strace -p <PID> to trace system calls for AIO operations. Look for io_getevents() calls without proper timeout handling.

Impact Analysis

This vulnerability can cause a persistent denial of service, making the affected application or thread unresponsive. It may lead to high CPU or memory usage due to the infinite loop, disrupting normal operations of applications using libkcapi's AIO interface.

Compliance Impact

This vulnerability primarily causes a denial of service by making applications unresponsive due to an infinite loop. It does not directly impact data confidentiality or integrity, which are key concerns for GDPR and HIPAA. However, prolonged denial of service could indirectly affect compliance by disrupting access to critical systems handling personal or health data.

Mitigation Strategies

Immediately stop using AIO in libkcapi if not required. If AIO is necessary, ensure handles are destroyed and reinitialized after any AIO completion error instead of reusing them. Avoid initializing handles with KCAPI_INIT_AIO.

Update libkcapi to a patched version if available. Monitor affected applications for persistent denial of service and restart unresponsive threads or processes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71227. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart