CVE-2026-130507
Description
A flaw was found in virglrenderer, the virtual OpenGL renderer used to provide 3D graphics acceleration to virtual machines. On the host-side buffer transfer path for GBM-backed resources, guest-supplied transfer parameters are not properly validated against the dimensions of the allocated buffer. A malicious guest with 3D acceleration enabled could use this flaw to perform an out-of-bounds write in the host renderer process, causing memory corruption, or an out-of-bounds read disclosing host memory to the guest. This could result in a denial of service of the renderer process or, potentially, a virtual machine escape. Only renderer configurations with GBM buffer allocation enabled are affected.
Statement
The affected code path requires the renderer to be built and configured with GBM buffer allocation active (upstream configurations such as crosvm/minigbm or Venus-interop setups; upstream development code as of 2026-11-11 has no fix). No shipped Red Hat product is affected: Red Hat Enterprise Linux 8 ships virglrenderer 0.8.2 with the affected code path compiled out, and the component is not included in Red Hat Enterprise Linux 9 or 10.
Mitigation
No Red Hat product requires mitigation: no shipped Red Hat product enables the affected code path. For affected configurations (renderer builds with GBM allocation active, e.g. crosvm/minigbm or Venus-interop setups): disable the GBM allocation feature (VIRGL_GBM_LAYOUT_DISABLE=true for generic libgbm builds, or run the renderer without Venus interop), or disable virgl 3D acceleration for guest GPUs until a fixed renderer is deployed.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.8 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Changed | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | High | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Red Hat CVSS v3 Score Explanation
Score for the demonstrated scenario in vulnerable configurations (guest attacker, GBM allocation active). PR:N variant (attacker controls the guest OS) is 9.3.
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Acknowledgements
Red Hat would like to thank Stuart Thomas for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.