CVE-2026-74443 — drm/vmwgfx: bound DMA command body size against suffix pointer
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < eb20f418933bea53375843b27b4022c1810be63b≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < fcd1e56e7816b31a1050ccc67df722b20f6bb15d≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < a4a37080a5ac777b59306cfcdf854cc05d7604d4≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < 036e16ada95389bdc30f41068af04c1d0872fad0≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < d5d7ada4e1296b00d89fe82b2ca850cc7809d6f7≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < 7e40e6120fb232a10b543ffd994e5c6d8f3a2cc6≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < 9759da60e38d7b9db44dc92713e4e0391883d221≥ 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < f4f1db96bfd68b81053693ba53405b6f510ac16c and 1 moreversion 2.6.33 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.0 | 6.0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 8.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/9759da60e38d7b9db44dc92713e4e0391883d221
- git.kernel.org/stable/c/fcd1e56e7816b31a1050ccc67df722b20f6bb15d
- git.kernel.org/stable/c/036e16ada95389bdc30f41068af04c1d0872fad0
- git.kernel.org/stable/c/a4a37080a5ac777b59306cfcdf854cc05d7604d4
- git.kernel.org/stable/c/d5d7ada4e1296b00d89fe82b2ca850cc7809d6f7
- git.kernel.org/stable/c/f4f1db96bfd68b81053693ba53405b6f510ac16c
- git.kernel.org/stable/c/eb20f418933bea53375843b27b4022c1810be63b
- git.kernel.org/stable/c/7e40e6120fb232a10b543ffd994e5c6d8f3a2cc6
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 15h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 15h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74443 is "drm/vmwgfx: bound DMA command body size against suffix pointer", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.