An out-of-bounds write issue was found in the VirGL virtual OpenGL renderer (virglrenderer).
Noroxi assessment
Priority: Monitor (action score 31/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.40% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: virglrenderer (Debian:10) 0.7.0-2+deb10u1; virglrenderer (Debian:12) 0.10.0-1; virglrenderer (openSUSE:Leap 15.3) 0.6.0-4.9.1.
Low priority for now. Upgrade to virglrenderer (Debian:10) 0.7.0-2+deb10u1; virglrenderer (Debian:12) 0.10.0-1; virglrenderer (openSUSE:Leap 15.3) 0.6.0-4.9.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
An out-of-bounds write issue was found in the VirGL virtual OpenGL renderer (virglrenderer). This flaw allows a malicious guest to create a specially crafted virgil resource and then issue a VIRTGPU_EXECBUFFER ioctl, leading to a denial of service or possible code execution.
- Published
- Aug 25, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
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.
| Vendor | Product | CPE |
|---|---|---|
| virglrenderer project | virglrenderer | cpe:2.3:a:virglrenderer_project:virglrenderer |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- redhat enterprise linux8.0
- virglrenderer project virglrenderer0.8.1 and later · before 0.10.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a virglrenderer
- virglrenderer 0.8.1 and afteraffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | virglrenderer | before 0.7.0-2+deb10u1 | 0.7.0-2+deb10u1 |
| Debian:12 | virglrenderer | before 0.10.0-1 | 0.10.0-1 |
| openSUSE:Leap 15.3 | virglrenderer | before 0.6.0-4.9.1 | 0.6.0-4.9.1 |
| SUSE:HPE Helion OpenStack 8 | virglrenderer | before 0.5.0-12.9.1 | 0.5.0-12.9.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP3 | virglrenderer | before 0.6.0-4.9.1 | 0.6.0-4.9.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP4 | virglrenderer | before 0.9.1-150400.3.3.1 | 0.9.1-150400.3.3.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP4 | virglrenderer | before 0.9.1-150400.3.3.1 | 0.9.1-150400.3.3.1 |
Same product
virglrenderer project: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-18389A heap-based buffer overflow in the vrend_renderer_transfer_write_iov function in vrend_renderer.c in virglrenderer through 0.8.0 allows gue31Monitor
- CVE-2019-18390An out-of-bounds read in the vrend_blit_need_swizzle function in vrend_renderer.c in virglrenderer through 0.8.0 allows guest OS users to ca28Monitor
- CVE-2017-5580The parse_instruction function in gallium/auxiliary/tgsi/tgsi_text.c in virglrenderer before 0.6.0 allows local guest OS users to cause a de28Monitor
- CVE-2016-10214Memory leak in the virgl_resource_attach_backing function in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of ser26Monitor
- CVE-2017-5937The util_format_is_pure_uint function in vrend_renderer.c in Virgil 3d project (aka virglrenderer) 0.6.0 and earlier allows local guest OS u26Monitor
- CVE-2016-10163Memory leak in the vrend_renderer_context_create_internal function in vrend_decode.c in virglrenderer before 0.6.0 allows local guest OS use26Monitor
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 |
|---|---|---|
| debian:virglrenderer | 0.10.0-1 · Debian:12 | Package registry (OSV) |
| opensuse:virglrenderer | 0.9.1-150400.3.3.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:virglrenderer | 0.5.0-12.9.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:virglrenderer | 0.9.1-150400.3.3.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP4 | Package registry (OSV) |
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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.