libkcapi: Use After Free
CVE-2026-71226 is a high-severity use after free vulnerability in libkcapi from Stephan Muelle, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 1.5.1 as the first without the flaw, so updating libkcapi to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update libkcapi to 1.5.1 or a later version.
- Read the advisory on access.redhat.com for workarounds and exact fixed builds.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA (redhat.com) |
| CVSS 3.1 | 7.3 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- access.redhat.com/errata/RHSA-2026:56985
- access.redhat.com/errata/RHSA-2026:67265
- access.redhat.com/errata/RHSA-2026:67266
- access.redhat.com/errata/RHSA-2026:67267
- access.redhat.com/errata/RHSA-2026:69285
- access.redhat.com/errata/RHSA-2026:87712
- access.redhat.com/errata/RHSA-2026:93453
- access.redhat.com/errata/RHSA-2026:94537
- access.redhat.com/errata/RHSA-2026:95346
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.