drm/vmwgfx: use check_add_overflow for shader size+offset bound (CVE-2026-80887) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80887

drm/vmwgfx: use check_add_overflow for shader size+offset bound

Answer in brief

CVE-2026-80887 records a Unknown severity vulnerability in drm/vmwgfx: use check_add_overflow for shader size+offset bound. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 4, 2026Updated Sep 4, 2026Source checked Sep 4, 2026First seen by HOL Sep 4, 2026Material review Sep 4, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=668b206601c5f5063e03b76784a0d3024fa2b249 <1bbe7751f5ebac383405ef29a66622d65bd505d3 \|\| >=668b206601c5f5063e03b76784a0d3024fa2b249 <d3f44438aa805270aaead3b6840ccaea0f4c11f9 \|\| >=668b206601c5f5063e03b76784a0d3024fa2b249 <cfd163169af3be56eaef113c680ea251f0d09189 \|\| >=668b206601c5f5063e03b76784a0d3024fa2b249 <5c725901908eb1e52a16fc0e2373cb761df42d21 \|\| >=668b206601c5f5063e03b76784a0d3024fa2b249 <54d56d5b42d2e4c72ba6e365e9774da90698aa22	1bbe7751f5ebac383405ef29a66622d65bd505d3, d3f44438aa805270aaead3b6840ccaea0f4c11f9, cfd163169af3be56eaef113c680ea251f0d09189, 5c725901908eb1e52a16fc0e2373cb761df42d21, 54d56d5b42d2e4c72ba6e365e9774da90698aa22
Linux/Linuxgeneric	6.4	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 1bbe7751f5ebac383405ef29a66622d65bd505d3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 4, 2026

Sources and claim methodology

Upstream source description

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: use check_add_overflow for shader size+offset bound vmw_shader_define() validates the user-supplied shader window against its backing buffer with (u64)buffer->tbo.base.size < (u64)size + (u64)offset drm_vmw_shader_create_arg::offset is __u64 in the uapi; when it is near U64_MAX the unsigned addition wraps and the resulting tiny value passes the check. The unbounded offset is then stored in res->guest_memory_offset and forwarded to host SVGA shader-create commands. Use check_add_overflow() to detect the wrap and compare the resulting endpoint against the buffer size.

Quoted source text, attributed separately from HOL analysis.