Skip to content
Systems

CVE-2026-74443

8.8
High
EPSS 0.13%Patch availableAug 17, 2026

Linux vmwgfx DMA parsing bug allows one command to overwrite another via TOCTOU

common questions

Is CVE-2026-74443 being exploited?

Not confirmed. CVE-2026-74443 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-74443?

CVE-2026-74443 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74443?

Yes. A fix has been recorded for CVE-2026-74443. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74443 affect?

CVE-2026-74443 affects Linux kernel (drm/vmwgfx module), VMware virtual GPU (vmwgfx). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74443?

Apply kernel/vmwgfx updates immediately; restrict access to GPU devices until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (drm/vmwgfx module)VMware virtual GPU (vmwgfx)
impact

Local attacker able to submit vmwgfx DMA commands can overwrite verified fields (GMR/surface id), enabling privilege escalation, GPU resource spoofing, or VM escape.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < eb20f418933bea53375843b27b4022c1810be63b
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < fcd1e56e7816b31a1050ccc67df722b20f6bb15d
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < a4a37080a5ac777b59306cfcdf854cc05d7604d4
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < 036e16ada95389bdc30f41068af04c1d0872fad0
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < d5d7ada4e1296b00d89fe82b2ca850cc7809d6f7
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < 7e40e6120fb232a10b543ffd994e5c6d8f3a2cc6
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < 9759da60e38d7b9db44dc92713e4e0391883d221
  • affected>= 4e4ddd47774313accc86b233d6ca2c6a9037a671 and < f4f1db96bfd68b81053693ba53405b6f510ac16c
  • affected2.6.33
vendor says fixed in< 2.6.33, >= 5.10.265 and <= 5.10.*, >= 5.15.216 and <= 5.15.*, >= 6.1.183 and <= 6.1.*, >= 6.6.151 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free