CVE-2026-80700

published 28 Aug 2026 · updated 20 Nov 2026

drm/vmwgfx: validate external BO copy bounds for both stride paths

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4e0f669e2951b742239c6fe847fcc406fe78748d, Kernel 5e4a2d15637a906cbd9bc98e0bf969f5f713e344, Kernel 706c93c5813caabbb0d0a576c017d15aeec2c113 and 7 more.

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: validate external BO copy bounds for both stride paths vmw_external_bo_copy() trusts caller-supplied offsets, strides, and heights and operates on imported dma-buf vmaps: - The equal-stride memcpy() bound was clamped after subtracting the offsets from dst_size and src_size; an offset larger than the BO size wraps the unsigned subtraction to a huge value and the resulting memcpy() runs off the end of the vmap. dst_stride * height is also a u32 multiplication that can overflow. - The non-equal-stride row-by-row path had no bound at all. The loop touches bytes through offset + (height - 1) * stride + width_in_bytes, with only a WARN_ON(dst_stride < width_in_bytes), and could likewise step past the end of either mapping. The offsets and strides are derived from STDU/SOU plane state, so a configured CRTC submitting a crafted atomic commit on an imported framebuffer can reach this path. Validate the exact row-copy endpoint against each BO's size up front using check_mul_overflow() and check_add_overflow(). Use the bulk memcpy() path only when width_in_bytes covers the whole stride; otherwise copy one row at a time so partial-row updates near the bottom of a framebuffer remain valid. Also reject zero strides and stride < width_in_bytes, both of which the row-by-row path cannot represent safely.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=9a9716bbbf3dd6b6cbefba3abcc89af8b72631f4 <4e0f669e2951b742239c6fe847fcc406fe78748d, >=50f1199250912568606b3778dc56646c10cb7b04 <5e4a2d15637a906cbd9bc98e0bf969f5f713e344, >=50f1199250912568606b3778dc56646c10cb7b04 <706c93c5813caabbb0d0a576c017d15aeec2c113, >=50f1199250912568606b3778dc56646c10cb7b04 <e7b25a6011781ebfdbc458552cae6d4156732771, >=6.10.8 <6.11, >=6.6.49 <6.6.151, =5c12391ee1ab59cb2f3be3f1f5e6d0fc0c2dc854, =6.11, >=50f1199250912568606b3778dc56646c10cb7b04 <042ca38779554687fc32b66a28328e0d9a36c58f4e0f669e2951b742239c6fe847fcc406fe78748d, 5e4a2d15637a906cbd9bc98e0bf969f5f713e344, 706c93c5813caabbb0d0a576c017d15aeec2c113, e7b25a6011781ebfdbc458552cae6d4156732771, 6.11, 6.6.151, 042ca38779554687fc32b66a28328e0d9a36c58f
linux-kernel: Kernel>=6.11.0 <6.12.103, >=6.13.0 <6.18.44, >=6.19.0 <7.1.8, >=6.6.49 <6.6.151, >=6.10.8 <6.116.12.103, 6.18.44, 7.1.8, 6.6.151, 6.11

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80700 severity on Zeptric[![CVE-2026-80700](https://zeptric.io/badge/cve/CVE-2026-80700.svg)](https://zeptric.io/cve/CVE-2026-80700)