CVE-2026-80887: drm/vmwgfx: use check_add_overflow for shader size+offset bound
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 1bbe7751f5ebac383405ef29a66622d65bd505d3, 54d56d5b42d2e4c72ba6e365e9774da90698aa22, 5c725901908eb1e52a16fc0e2373cb761df42d21; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
Low priority for now. Upgrade to Linux Linux 1bbe7751f5ebac383405ef29a66622d65bd505d3, 54d56d5b42d2e4c72ba6e365e9774da90698aa22, 5c725901908eb1e52a16fc0e2373cb761df42d21; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: use check_add_overflow for shader size+offset bound vmw_shader_define() validates the user-supplied shader window against its backing buffer with (u64)buffer->tbo.base.size < (u64)size + (u64)offset drm_vmw_shader_create_arg::offset is __u64 in the uapi; when it is near U64_MAX the unsigned addition wraps and the resulting tiny value passes the check. The unbounded offset is then stored in res->guest_memory_offset and forwarded to host SVGA shader-create commands. Use check_add_overflow() to detect the wrap and compare the resulting endpoint against the buffer size.
- Published
- Sep 4, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.4affected
- 668b206601c5f5063e03b76784a0d3024fa2b249 and later · before 1bbe7751f5ebac383405ef29a66622d65bd505d3affected · git
- 668b206601c5f5063e03b76784a0d3024fa2b249 and later · before d3f44438aa805270aaead3b6840ccaea0f4c11f9affected · git
- 668b206601c5f5063e03b76784a0d3024fa2b249 and later · before cfd163169af3be56eaef113c680ea251f0d09189affected · git
- 668b206601c5f5063e03b76784a0d3024fa2b249 and later · before 5c725901908eb1e52a16fc0e2373cb761df42d21affected · git
- 668b206601c5f5063e03b76784a0d3024fa2b249 and later · before 54d56d5b42d2e4c72ba6e365e9774da90698aa22affected · git
- before 6.4not affected · semver
- 6.6.151 and later · up to and including 6.6.*not affected · semver
- 6.12.103 and later · up to and including 6.12.*not affected · semver
- 6.18.44 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.68.1.el10_2 | 6.12.0-211.68.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80883Sep 4, 2026 · drm/tegra: gr2d/gr3d: Initialize address register map before HOST1X client is registered0Monitor
- ← EarlierCVE-2026-80884Sep 4, 2026 · ntb: Store original DMA address for future release0Monitor
- Later →CVE-2026-80888Sep 4, 2026 · drm/vmwgfx: drop dma_buf reference on foreign-fd prime import0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1bbe7751f5ebac383405ef29a66622d65bd505d3 | Vendor (CNA) |
| Linux Linux | 54d56d5b42d2e4c72ba6e365e9774da90698aa22 | Vendor (CNA) |
| Linux Linux | 5c725901908eb1e52a16fc0e2373cb761df42d21 | Vendor (CNA) |
| Linux Linux | cfd163169af3be56eaef113c680ea251f0d09189 | Vendor (CNA) |
| Linux Linux | d3f44438aa805270aaead3b6840ccaea0f4c11f9 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.173.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.173.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules-core | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-modules-extra | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 5.14.0-687.57.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-rt | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.173.1.rt7.514.el8_10 · AlmaLinux:8 | Package registry (OSV) |
+16
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.