Finding and attribution
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.
Product: libkcapi. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE; Red Hat.
CVE identifiers: CVE-2026-71226.
AI and human contribution (source account): AISLE’s public CVE index labels this case among findings discovered by its AI-native engine. This is the company’s case-list attribution; the specific model, degree of automation and division of work between AI and people are not identified in the cited sources. The CNA credits: This issue was discovered by Found by AISLE in partnership with Red Hat.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary CNA record was published 2026-08-05. The reviewed sources do not establish whether the issue was known to defenders before disclosure or exploited in the wild; this classification does not make a zero-day or non-exploitation claim.
Remediation status: fix documented. The primary CNA affected-version data marks libkcapi: 0:1.5.1-1.el10_2, libkcapi: 0:1.5.0-6.el10_0, libkcapi: 0:1.4.0-3.el8_10, libkcapi: 0:1.2.0-3.el8_8.1, libkcapi: 0:1.4.0-3.el9_8 (plus 4 additional branch build(s)) as unaffected. The CNA references https://access.redhat.com/errata/RHSA-2026:56985. This is product/branch-specific and does not establish deployment or resolve other affected branches.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 5 Aug 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.3. Documented technical effects: other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-71226: CVSS 3.1 · 7.3 (High) ·
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H. CVE Program CNA record · checked 17 Nov 2026.
CVE-2026-71226: other.
Prerequisites / affected scope: No additional exploit precondition is stated beyond the affected software and versions in the CNA description..
Exploitation evidence: Exploitation status is not stated in the reviewed CNA/advisory evidence.. Impact source · checked 17 Nov 2026.
Documented fix: The primary CNA affected-version data marks libkcapi: 0:1.5.1-1.el10_2, libkcapi: 0:1.5.0-6.el10_0, libkcapi: 0:1.4.0-3.el8_10, libkcapi: 0:1.2.0-3.el8_8.1, libkcapi: 0:1.4.0-3.el9_8 (plus 4 additional branch build(s)) as unaffected. The CNA references https://access.redhat.com/errata/RHSA-2026:56985. This is product/branch-specific and does not establish deployment or resolve other affected branches.