In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
drm\/virtio: fix memory leak of fence event on execbuffer failure<\/p>\n
virtio_gpu_execbuffer_ioctl() reserves a DRM event with
\ndrm_event_reserve_init() when VIRTGPU_EXECBUF_RING_IDX selects a ring that
\nuserspace has enabled polling for. virtio_gpu_init_submit() does this
\nbefore the BO handles, the command buffer, the syncobj arrays and the
\nin-fence are processed, so every later error path runs with the event
\nalready pending, including plain argument validation failures such as an
\ninvalid bo_handle or an in-syncobj that carries no fence.<\/p>\n
On those paths, virtio_gpu_cleanup_submit() drops the out-fence without
\ncancelling the event. The fence is freed without ever having been emitted,
\ntaking the only driver-side pointer to the event with it. Closing the DRM
\nfile does not help. drm_events_release() unlinks pending events but
\ndeliberately leaves the freeing to the driver’s later drm_send_event(),
\nwhich never runs for an orphaned event, so the allocation is leaked
\npermanently.<\/p>\n
Found when fuzzing the virtio driver with Syzkaller:<\/p>\n
\tBUG: memory leak
\n\tunreferenced object 0xffff88802c176e80 (size 96):
\n\tcomm “syz.1.367”, pid 10561, jiffies 4294960122
\n\thex dump (first 32 bytes):
\n\t\t00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
\n\t\tc8 6e 17 2c 80 88 ff ff 00 00 00 00 00 00 00 00 .n.,…………
\n\tbacktrace (crc e1973c6b):
\n\t\tkmemleak_alloc_recursive include\/linux\/kmemleak.h:44 [inline]
\n\t\tslab_post_alloc_hook mm\/slub.c:4597 [inline]
\n\t\tslab_alloc_node mm\/slub.c:4917 [inline]
\n\t\t__kmalloc_cache_noprof+0x49d\/0x6f0 mm\/slub.c:5485
\n\t\t_kmalloc_noprof include\/linux\/slab.h:988 [inline]
\n\t\t_kzalloc_noprof include\/linux\/slab.h:1309 [inline]
\n\t\tvirtio_gpu_fence_event_create drivers\/gpu\/drm\/virtio\/virtgpu_submit.c:282 [inline]
\n\t\tvirtio_gpu_init_submit drivers\/gpu\/drm\/virtio\/virtgpu_submit.c:398 [inline]
\n\t\tvirtio_gpu_execbuffer_ioctl+0xbbf\/0x1aa0 drivers\/gpu\/drm\/virtio\/virtgpu_submit.c:505
\n\t\tdrm_ioctl_kernel+0x1f4\/0x3e0 drivers\/gpu\/drm\/drm_ioctl.c:817
\n\t\tdrm_ioctl+0x5f4\/0xc70 drivers\/gpu\/drm\/drm_ioctl.c:914
\n\t\tvfs_ioctl fs\/ioctl.c:51 [inline]
\n\t\t__do_sys_ioctl fs\/ioctl.c:597 [inline]
\n\t\t__se_sys_ioctl fs\/ioctl.c:583 [inline]
\n\t\t__x64_sys_ioctl+0x18e\/0x210 fs\/ioctl.c:583
\n\t\tdo_syscall_x64 arch\/x86\/entry\/syscall_64.c:63 [inline]
\n\t\tdo_syscall_64+0x116\/0x800 arch\/x86\/entry\/syscall_64.c:94
\n\t\tentry_SYSCALL_64_after_hwframe+0x77\/0x7f<\/p>\n
Fix by cancelling and freeing the DRM event on the execbuffer error path
\nbefore dropping the fence. Clear the fence’s event pointer after
\ncancellation so it does not retain a dangling pointer.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
drm\/virtio: fix memory leak of fence event on execbuffer failure<\/p>\n
virtio_gpu_execbuffer_ioctl() reserves a DRM event with
\ndrm_event<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-40981","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/40981","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=40981"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=40981"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=40981"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}