https://vulnerability.circl.lu/sightings/feed 2026-05-05T23:13:13.392349+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/3950cab4-903d-4fce-8cfd-4cd1324d4d77/export 2026-05-05T23:13:13.826825+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "3950cab4-903d-4fce-8cfd-4cd1324d4d77", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50134", "type": "seen", "source": "https://t.me/cvedetector/9912", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50134 - Oracle VirtualBox Scatter Write Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-50134 \nPublished : Nov. 5, 2024, 6:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/vboxvideo: Replace fake VLA at end of vbva_mouse_pointer_shape with real VLA \n \nReplace the fake VLA at end of the vbva_mouse_pointer_shape shape with \na real VLA to fix a \"memcpy: detected field-spanning write error\" warning: \n \n[ 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) \n[ 13.319841] WARNING: CPU: 0 PID: 1105 at drivers/gpu/drm/vboxvideo/hgsmi_base.c:154 hgsmi_update_pointer_shape+0x192/0x1c0 [vboxvideo] \n[ 13.320038] Call Trace: \n[ 13.320173] hgsmi_update_pointer_shape [vboxvideo] \n[ 13.320184] vbox_cursor_atomic_update [vboxvideo] \n \nNote as mentioned in the added comment it seems the original length \ncalculation for the allocated and send hgsmi buffer is 4 bytes too large. \nChanging this is not the goal of this patch, so this behavior is kept. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"05 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T19:44:11.000000Z"} 2024-11-05T19:44:11+00:00