CVE-2026-80701

Technical Description

In the Linux kernel, the following vulnerability has been resolved:

drm/vmwgfx: enforce cursor size limits for MOB cursors

vmw_cursor_plane_atomic_check() bounds cursor width and height only

on the legacy update path; the SVGA_CAP2_CURSOR_MOB path -- the

default on modern hosts -- accepts any size. When the requested size

exceeds SVGA_REG_CURSOR_MAX_DIMENSION or SVGA_REG_MOB_MAX_SIZE,

vmw_cursor_mob_get() returns -EINVAL and leaves vps->cursor.mob NULL.

Its return value is then discarded in vmw_cursor_plane_prepare_fb(),

so the subsequent vmw_cursor_update_mob() calls

vmw_bo_map_and_cache(NULL) and oopses inside

vmw_bo_map_and_cache_size() on the tbo.base.size load.

Reachable from any DRM master via DRM_IOCTL_MODE_CURSOR2 with a

sufficiently large width or height (e.g. cursor_max_dim + 1).

Reject oversized cursors in atomic_check for both MOB-backed cursor

update types. The MOB byte-size limit only applies to the

SVGA_CAP2_CURSOR_MOB path (vmw_cursor_mob_size() returns 0 for

GB_O

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References