# CVE-2026-74443: drm/vmwgfx: bound DMA command body size against suffix pointer

> A race condition in the vmwgfx driver allows attackers to corrupt command stream fields, potentially leading to privilege escalation or code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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-96336, BELL-CVE-2026-74443, DEBIAN-CVE-2026-74443, GHSA-hrvm-q452-gmcq, UBUNTU-CVE-2026-74443

## What is CVE-2026-74443?

CVE-2026-74443 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: bound DMA command body size against suffix pointer

vmw_cmd_dma() locates the DMA suffix at

	(unsigned long) &cmd->body + header->size - sizeof(*suffix)

without checking that header->size is large enough to contain both
cmd->body and the suffix.  An undersized header makes the suffix
pointer underflow back into the previous command in the bounce
buffer.  The verifier later writes suffix->maximumOffset, clobbering
verified fields of an already-relocated earlier command -- a TOCTOU
on the device-visible command stream that lets one command rewrite
another's GMR id, surface id, or other authenticated fields.

Reject the command if the body is too small for the suffix to fit.

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


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

Apply the vendor's patch.

## Is CVE-2026-74443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74443 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-74443 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-74443/ (Markdown: https://insights.sbomify.com/CVE-2026-74443/index.md)
```

## Sources

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

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