Skip to content
VulniPulse
Advisory severityMedium5.1Red Hat Linux

Medium [CVE-2026-71227] Infinite loop denial of service in libkcapi _kcapi_aio_read_all due to unhandled io_getevents timeout return

This medium-severity Red Hat Linux advisory covers CVE-2026-71227 affecting Red Hat Hardened Images, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-71227 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Infinite loop denial of service in libkcapi _kcapi_aio_read_all() due to unhandled io_getevents() timeout return. Red Hat rates this moderate (CVSS 5.1).

Weakness: CWE-835. Red Hat lists fixing advisory RHSA-2026:56985 with package libkcapi-main-1.5.1-0.1.hum1.

Affected products named by the advisory: Red Hat Hardened Images; Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; and 1 more.

Affected products named by the advisory: Red Hat OpenShift Container Platform 4; Red Hat Enterprise Linux 10.0 Extended Update Support.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • libkcapi-main-1.5.1-0.1.hum1
  • RHSA-2026:56985

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, applications should avoid initializing `libkcapi` handles with `KCAPI_INIT_AIO` if AIO functionality is not strictly required. If AIO must be used, applications should destroy and reinitialize `libkcapi` handles after any AIO completion error, rather than reusing them for subsequent AIO operations.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.