CVE-2026-80701

published 28 Aug 2026 · updated 15 Nov 2026

drm/vmwgfx: enforce cursor size limits for MOB cursors

5.0MediumEPSS 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 1eb4f796695be39e0b5c4383350033ced9ade703, Kernel 9109b7935b9c058b75348610ef8437c52f9020e3, Kernel d5ed8749168ad13c0dbaa8300f68d854b6076966 and 2 more.

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_ONLY); compute the required MOB size in 64-bit to avoid overflow when very large dimensions are requested. In prepare_fb only call vmw_cursor_mob_get()/_map() for VMW_CURSOR_UPDATE_MOB -- the GB_ONLY path uses bo->map.virtual directly and would otherwise be silently downgraded to NONE on hosts without SVGA_CAP2_CURSOR_MOB (where vmw_cursor_mob_get() always returns -EINVAL). Degrade the update to NONE if vmw_cursor_mob_get() or vmw_cursor_mob_map() fails so the update path does not run with a NULL backing MOB.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.16, >=965544150d1cadf0e8f5bb6c13c19697e46e1429 <1eb4f796695be39e0b5c4383350033ced9ade703, >=965544150d1cadf0e8f5bb6c13c19697e46e1429 <9109b7935b9c058b75348610ef8437c52f9020e3, >=965544150d1cadf0e8f5bb6c13c19697e46e1429 <d5ed8749168ad13c0dbaa8300f68d854b60769661eb4f796695be39e0b5c4383350033ced9ade703, 9109b7935b9c058b75348610ef8437c52f9020e3, d5ed8749168ad13c0dbaa8300f68d854b6076966
linux-kernel: Kernel>=6.16.0 <6.18.44, >=6.19.0 <7.1.86.18.44, 7.1.8

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-80701 severity on Zeptric[![CVE-2026-80701](https://zeptric.io/badge/cve/CVE-2026-80701.svg)](https://zeptric.io/cve/CVE-2026-80701)