Incorrect memory access via double-offset log mapping
Published Oct 14, 2026 · Updated Oct 14, 2026
DPDK lib/vhost allows local users to cause incorrect memory access through a double-offset error in log mapping calculations. The calculation counts an offset twice; Red Hat does not publish the affected function or identify the resulting read or write operation. Exploitation requires low local privileges, but the advisory does not establish a specific crash mode or demonstrate code execution.
Summary
What happened
DPDK lib/vhost allows local users to cause incorrect memory access through a double-offset error in log mapping calculations. The calculation counts an offset twice; Red Hat does not publish the affected function or identify the resulting read or write operation. Exploitation requires low local privileges, but the advisory does not establish a specific crash mode or demonstrate code execution.
The record
- CVE
- CVE-2026-86563
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- libuser Project
- Product
- Red Hat OpenShift Container Platform 4
- Classifications
- CWE-131
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started