Bug 2574283 - CVE-2026-130507 virglrenderer: virglrenderer: guest-triggerable OOB write/read in GBM direct-transfer path [fedora-all]
Summary: CVE-2026-130507 virglrenderer: virglrenderer: guest-triggerable OOB write/rea...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: virglrenderer
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["5c6a4cac-404e-45d8-a8d6-9...
Depends On:
Blocks: CVE-2026-130507
TreeView+ depends on / blocked
 
Reported: 2026-11-17 10:57 UTC by Thibault Guittet
Modified: 2026-11-17 10:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thibault Guittet 2026-11-17 10:57:26 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Stuart Thomas reported via JSM (PSIRTSUPT-30502, 2026-11-13, responsible disclosure, not published elsewhere) a guest-to-host out-of-bounds write and read in virglrenderer's vrend GBM direct-transfer path.

In vrend_renderer_transfer_internal() (src/vrend/vrend_renderer.c), the GBM fast path calls virgl_gbm_transfer() and returns before the resource_contains_box() and check_iov_bounds() validations run. virgl_gbm_transfer() (src/vrend/vrend_winsys_gbm.c) derives the copy offset (host_resource_offset) and row count from the guest-controlled pipe_box without validating them against the gbm buffer object's dimensions, so a malicious guest can memcpy past the mapped bo via VIRGL_CCMD_TRANSFER_TO_HOST (host heap out-of-bounds WRITE of attacker-controlled bytes) and VIRGL_CCMD_TRANSFER_FROM_HOST (out-of-bounds READ copied back to the guest) on a GBM-backed (SCANOUT/SHARED-bound) resource. box->x/box->y are signed and unvalidated on this path, so the write start offset is attacker-arbitrary.

Confirmed by source audit and reproduced end-to-end under ASan (vtest transport, virglrenderer 1.3.0): heap-buffer-overflow WRITE and READ of 256-byte rows past a 16 KiB gbm bo mapping in virgl_gbm_transfer_internal(), reached through vrend_renderer_transfer_internal's early-return fast path. Single-variable negative control (in-bounds box) completes cleanly with data round-trip verified.

Affected configurations: builds with ENABLE_GBM_ALLOCATION + EGL and the GBM allocation path active -- minigbm builds (ChromeOS crosvm/ARCVM) always; generic libgbm builds with the gbm layout feature / Venus interop active (host/embedder configuration). Upstream main has no fix as of commit 01637fc (2026-11-11); the vulnerable code is identical in the 1.3.0 release.

Red Hat exposure: none. RHEL 8 ships virglrenderer 0.8.2 with the GBM allocation feature compiled out (meson option gbm_allocation default false, not enabled in the spec); the component is not shipped in RHEL 9 or 10.

CVSS 3.1 (vulnerable configurations): 8.8 -- AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (PR:N / attacker controls the guest OS: 9.3).


Note You need to log in before you can comment on or make changes to this bug.