Destination process crash via signed size conversion
Published Aug 10, 2026 · Updated Aug 10, 2026
Type mismatch in QEMU vhost inflight migration allows remote authenticated users to crash the destination QEMU process. The VMS_VBUFFER load path reads a uint64_t inflight size as int32_t, converts a negative result to size_t, and makes qemu_get_buffer() overrun its mmap-backed region. Exploitation requires control of the migration producer or write access to its channel, a little-endian destination, and configured vhost inflight migration.
Summary
What happened
Type mismatch in QEMU vhost inflight migration allows remote authenticated users to crash the destination QEMU process. The VMS_VBUFFER load path reads a uint64_t inflight size as int32_t, converts a negative result to size_t, and makes qemu_get_buffer() overrun its mmap-backed region. Exploitation requires control of the migration producer or write access to its channel, a little-endian destination, and configured vhost inflight migration.
The record
- CVE
- CVE-2026-6426
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-681, T1499.004
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo