CVE-2024-50134: drm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape with real VLA
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.
Security readout for executives and security teams
Plain-English summary
CVE-2024-50134 is a Linux kernel issue in the VirtualBox video driver. The fix changes how mouse pointer shape data is represented to stop a kernel memcpy field-spanning write warning. Business exposure is mainly Linux systems using affected kernels with this driver path, especially virtualized environments.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize patching on VirtualBox-based Linux workloads and appliances covered by vendor advisories, while tracking for any later exploitability updates.
Technical view
The affected code is in drm/vboxvideo, specifically vbva_mouse_pointer_shape handling in hgsmi_update_pointer_shape. The kernel fix replaces a fake variable-length array at the end of the structure with a real VLA while preserving an existing buffer length behavior that appears four bytes large.
Likely exposure
Exposure appears limited to Linux kernels carrying the affected vboxvideo driver code. Systems not using VirtualBox video functionality are less likely to encounter the vulnerable path, but the source bundle does not provide a complete exploitability assessment.
Exploitation context
No active exploitation is stated in the supplied sources, and this CVE is not listed as KEV in the bundle. The provided description shows a detected kernel warning, not a public exploit chain or attacker workflow.
Researcher notes
The source bundle lacks CVSS, CWE, and exploitability detail. Analysis should focus on affected kernel branches, downstream vendor backports, and whether the vboxvideo cursor update path is reachable in your environment.
Mitigation direction
Update affected Linux kernels using distribution or vendor security updates.
Apply relevant stable kernel fixes when maintaining custom kernels.
Review Debian LTS and Siemens advisories where applicable.
If patching is delayed, check vendor guidance for supported temporary mitigations.
Validation and detection
Inventory Linux systems and kernel versions against affected package advisories.
Check whether vboxvideo is present or used on virtualized Linux hosts.
Confirm vendor kernel updates include the referenced stable commits.
Review kernel logs for related vboxvideo memcpy field-spanning write warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-50134 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
2ADP providers
11Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Nov 5, 2024, 17:10 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.