[Bug]: VirtualBoxVM crashes inside the host AMD graphics driver when the guest desktop renders images

Aperta
#987 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c

Direzione di ricerca

Start by reading the VMSVGA 3D support code and the VBox.log exception record described in the report, then inspect how guest image surfaces are sent through the host graphics path. The AMD driver is identified as the faulting code, and the payload does not name a VirtualBox source file or failing test. Done means identifying whether VirtualBox can prevent the out-of-bounds driver read or otherwise keep the VM responsive.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
Version

7.2.22

Host OS Type

Windows

Host OS name + version

Windows 10 Home 22H2 (build 19045.6466), 64-bit

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

Kali Linux 2026.2 (64-bit, Debian-based), XFCE 4.20, Xorg at depth 24 (32 bpp effective)

Component

3D Support

What happened?

While a VM runs with VMSVGA + 3D on a Windows 10 host with an AMD Radeon RX 5700 XT (driver 26.10.2 /
32.0.21045.20006; the same fault was first captured on 32.0.21045.16010 at +0xF8B892),
VirtualBoxVM.exe takes a read access violation inside the host AMD user-mode driver, not inside VirtualBox code,
and the VM becomes unresponsive. The Windows dialog shows:

VirtualBoxVM.exe - Application Error
The instruction at 0x00007FFA7623B892 referenced memory at 0x00000021E80F42000.
The memory could not be read.

VirtualBox's own exception filter logs the exception and keeps the process alive but hung, so the guest display
freezes and the VM has to be killed. VBox.log contains the rtR3WinUnhandledXcptFilter record with a full
register dump and a resolved module/offset stack.

The faulting instruction is movzx r8d, byte ptr [rdx+2] at amdxx64.dll+0xF8B892 (a second compiled form of the
same copy exists at +0xF8B88F, movzx ecx, word ptr [rdx]). Both are 24-bit pixel copy helpers called from a row
loop at amdxx64.dll+0x6BD51. In every captured crash the containing private allocation ends exactly at the
faulting address, i.e. an out-of-bounds read of 1-2 bytes past a private PAGE_READWRITE allocation; the page after
it is MEM_RESERVE, which is why the read faults instead of silently succeeding. The same fault reproduces on the
current optional release 32.0.21045.20006 (AMD Software 26.10.2) at amdxx64.dll+0xF8BA12 (word form
+0xF8BA0F), so it is present in the newest driver available for this card.

The two row strides are related in every capture (58 of 58): r15 = ceil4(r14), i.e. the destination row is the
source row rounded up to a 4-byte boundary, so the difference is always exactly 3 bytes. The loop copies the source
row and then a second time for that 3-byte gap, reading from just past the source row - harmless on every row but
the last, where those bytes are past the allocation. Why the source row length itself has that value is not
identified from the logs; that does not change the defect.

Control: with 3D acceleration disabled the same workload produced no fault in 343 cycles, while with 3D enabled the
fault appeared from 49 s (GPU loaded) to 54 min (VM idle, one dialog open) across 58 captures.

Filing here because it is VirtualBox's process that dies and VirtualBox's handler that surfaces it; the faulting
code belongs to the AMD driver. The same report was submitted to AMD through the AMD Bug Report Tool on
2026-11-17, with the same evidence package.

Expected behavior: The guest desktop renders its dialogs and thumbnails and the VM keeps running.

Actual behavior: VirtualBoxVM.exe takes a read access violation inside the host GPU driver; VirtualBox's exception filter hangs the
process and the VM has to be killed.

Attached: amd-vbox-crash-evidence.zip (62 logs, 67 address-space maps, screenshots, scripts) and evidence-crash-video.mp4 - a 33-second recording of one fault with the host VBox.log live on the left and the VM window on the right.

amd-vbox-crash-evidence.zip

How can we reproduce this?
  1. Host: Windows 10 19045.6466, AMD RX 5700 XT, driver 32.0.21045.20006 (AMD Software 26.10.2). No integrated GPU is present, so the display path cannot fall back.
  2. VirtualBox 7.2.22; VM with display controller VMSVGA, "Enable 3D Acceleration" on. Video memory is not critical: the captures were made with 141 MB (51), 179 MB (9) and 256 MB (2), so any value that lets 3D acceleration work is fine. Guest: Kali Linux 2026.2 with XFCE (Xorg at depth 24). The Extension Pack is not required.
  3. Log in to the guest; the X11 desktop must be up (XFCE, Xorg at depth 24 in our captures). A bare desktop with no windows open is not enough in our experience - the fault needs windows that make the guest generate image surfaces, which step 5 covers.
  4. Optional, only to get a hit quickly: load the host GPU with a WebGL page (two browser windows, any heavy WebGL demo; measured 76-78% utilisation). CPU load alone also reaches the fault, just slower.
  5. In the guest, repeatedly open views that force thumbnail/image-surface generation: the file chooser on a folder of images, or the desktop settings -> background folder selector (Folder: -> Other location...) pointed at a directory of images. The selector/dialog is the reliable trigger; opening the settings window alone is not.
  6. Typically within 1-3 minutes the host shows the Application Error dialog. Timing measured on this machine: with GPU load, 3 of 5 runs faulted within 180 s (68, 75, 76 s), fastest 49 s and 2 min 40 s on the 26.10.2 capture; with CPU-only load, 2-8 minutes; with no host load at all, left running with one dialog open, captures at 51 and 54 minutes.

https://github.com/user-attachments/assets/2fef91c0-75ed-44df-b394-06d301e3ba3f

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Lingua principale
C
Stelle
1.4k
Fork
219
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di VirtualBox/virtualbox

Tutte le issue di VirtualBox/virtualbox

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.