Skip to main content
VulnerabilityPublished Updated

CVE-2026-80887: Linux kernel · drm/vmwgfx: use check_add_overflow for shader size+offset bound

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d3f44438aa805270aaead3b6840ccaea0f4c11f9 : patch Linux kernel soon.

Data as of 6 Nov 2026, 17:34 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d3f44438aa805270aaead3b6840ccaea0f4c11f9, cfd163169af3be56eaef113c680ea251f0d09189, 54d56d5b42d2e4c72ba6e365e9774da90698aa22 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 668b206601c5f5063e03b76784a0d3024fa2b249, < d3f44438aa805270aaead3b6840ccaea0f4c11f9
Fixed in
  • d3f44438aa805270aaead3b6840ccaea0f4c11f9
LinuxLinuxAffected
  • ≥ 668b206601c5f5063e03b76784a0d3024fa2b249, < cfd163169af3be56eaef113c680ea251f0d09189
Fixed in
  • cfd163169af3be56eaef113c680ea251f0d09189
LinuxLinuxAffected
  • ≥ 668b206601c5f5063e03b76784a0d3024fa2b249, < 54d56d5b42d2e4c72ba6e365e9774da90698aa22
Fixed in
  • 54d56d5b42d2e4c72ba6e365e9774da90698aa22
LinuxLinuxAffected
  • ≥ 668b206601c5f5063e03b76784a0d3024fa2b249, < 5c725901908eb1e52a16fc0e2373cb761df42d21
Fixed in
  • 5c725901908eb1e52a16fc0e2373cb761df42d21
LinuxLinuxAffected
  • ≥ 668b206601c5f5063e03b76784a0d3024fa2b249, < 1bbe7751f5ebac383405ef29a66622d65bd505d3
Fixed in
  • 1bbe7751f5ebac383405ef29a66622d65bd505d3
LinuxLinuxAffected
  • =6.4
Fixed in–

AI-suggested

A fix is available and has been applied in the Linux kernel. Users should update to the fixed versions identified by the commits d3f44438aa805270aaead3b6840ccaea0f4c11f9, cfd163169af3be56eaef113c680ea251f0d09189, 54d56d5b42d2e4c72ba6e365e9774da90698aa22, 5c725901908eb1e52a16fc0e2373cb761df42d21, and 1bbe7751f5ebac383405ef29e66622d65bd505d3. Applying these patches will prevent the overflow and ensure proper validation of shader size and offset.

Description

A vulnerability in the Linux kernel's vmwgfx driver involves improper handling of user-supplied shader window size and offset values. The flaw arises because the addition of size and offset can overflow, causing an incorrect boundary check to pass. This allows an unbounded offset to be used in shader creation commands, potentially leading to out-of-bounds memory access. The issue is fixed by using check_add_overflow() to detect addition overflow and properly validate the shader window against the buffer size.

References

Community reviews

Loading reviews…