Kernel memory corruption via clobbered allocation size
Published Aug 28, 2026 · Updated Aug 28, 2026
Out-of-bounds memory access in Linux vmwgfx allows attackers to corrupt kernel memory during graphics resource revalidation. vmw_resource_release() and vmw_resource_unbind_list() write Boolean values into guest_memory_size instead of guest_memory_dirty, reducing an allocation size to 0 or 1 and causing later bitmap walks to become zero-length or wrap out of bounds. Reachability requires the vmwgfx VMware virtual GPU driver and a release or unbind followed by resource revalidation; the upstream record does not establish code execution or privilege escalation.
Summary
What happened
Out-of-bounds memory access in Linux vmwgfx allows attackers to corrupt kernel memory during graphics resource revalidation. vmw_resource_release() and vmw_resource_unbind_list() write Boolean values into guest_memory_size instead of guest_memory_dirty, reducing an allocation size to 0 or 1 and causing later bitmap walks to become zero-length or wrap out of bounds. Reachability requires the vmwgfx VMware virtual GPU driver and a release or unbind followed by resource revalidation; the upstream record does not establish code execution or privilege escalation.
The record
- CVE
- CVE-2026-80702
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.4
- Affected versionversion=668b206601c5f5063e03b76784a0d3024fa2b249 <21bbe38faee4a195d33a93e3908e307807f7745d
- Affected versionversion=668b206601c5f5063e03b76784a0d3024fa2b249 <282f261cb035e5f01a486f76d356b7e9dbfba73f
- Affected versionversion=668b206601c5f5063e03b76784a0d3024fa2b249 <3b2bb16a5b622867140d69925db411ac8ecb3b2b
- Affected versionversion=668b206601c5f5063e03b76784a0d3024fa2b249 <83195b778f2d109a3a4f3ffaba4dce7e4cdb58aa
- Affected versionversion=668b206601c5f5063e03b76784a0d3024fa2b249 <9d6cbb76fe9cd760351f6b0b20f1bf788eab8fa6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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