# CVE-2026-74444: drm/vmwgfx: validate DRAW_PRIMITIVES header size before division

> A local attacker can trigger an integer overflow in the vmwgfx driver to read kernel memory out of bounds.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-96234, BELL-CVE-2026-74444, DEBIAN-CVE-2026-74444, GHSA-m498-64hg-9w93, UBUNTU-CVE-2026-74444

## What is CVE-2026-74444?

CVE-2026-74444 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

drm/vmwgfx: validate DRAW_PRIMITIVES header size before division

vmw_cmd_draw() computes

	maxnum = (header->size - sizeof(cmd->body)) / sizeof(*decl);

where header->size is u32 and is taken straight from the user-supplied
command stream.  When header->size is less than sizeof(cmd->body) the
unsigned subtraction wraps to nearly 4 GiB, producing a huge maxnum.
Any user-controlled cmd->body.numVertexDecls then passes the bound and
the loop dereferences decl[i] far past the end of the kernel command
bounce buffer, producing an out-of-bounds read of kernel memory.

Reject undersized headers up front.

## Which versions are affected by CVE-2026-74444?


## How do I fix CVE-2026-74444?

Apply the vendor's patch.

## Is CVE-2026-74444 being exploited?

There is no known exploitation of CVE-2026-74444 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74444 and fix it if it is affected.

What it is: CVE-2026-74444 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74444 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74444/ (Markdown: https://insights.sbomify.com/CVE-2026-74444/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74444
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74444
- OSV: https://osv.dev/vulnerability/CVE-2026-74444

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74444/
Summaries are generated and may contain mistakes; the official description above is the record.