drm/vmwgfx: validate external BO copy bounds for both stride paths
Summary
| CVE | CVE-2026-80700 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-28 08:16:55 UTC |
| Updated | 2026-08-28 08:16:55 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 9a9716bbbf3dd6b6cbefba3abcc89af8b72631f4 4e0f669e2951b742239c6fe847fcc406fe78748d git |
Not specified |
| CNA |
Linux |
Linux |
affected 50f1199250912568606b3778dc56646c10cb7b04 e7b25a6011781ebfdbc458552cae6d4156732771 git |
Not specified |
| CNA |
Linux |
Linux |
affected 50f1199250912568606b3778dc56646c10cb7b04 042ca38779554687fc32b66a28328e0d9a36c58f git |
Not specified |
| CNA |
Linux |
Linux |
affected 50f1199250912568606b3778dc56646c10cb7b04 5e4a2d15637a906cbd9bc98e0bf969f5f713e344 git |
Not specified |
| CNA |
Linux |
Linux |
affected 50f1199250912568606b3778dc56646c10cb7b04 706c93c5813caabbb0d0a576c017d15aeec2c113 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5c12391ee1ab59cb2f3be3f1f5e6d0fc0c2dc854 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.6.49 6.6.151 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.10.8 6.11 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.11 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.11 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.151 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.103 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.44 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.8 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/e7b25a6011781ebfdbc458552cae6d4156732771 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/706c93c5813caabbb0d0a576c017d15aeec2c113 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5e4a2d15637a906cbd9bc98e0bf969f5f713e344 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/042ca38779554687fc32b66a28328e0d9a36c58f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4e0f669e2951b742239c6fe847fcc406fe78748d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.