CVE-2026-98509UNKNOWNMITRENVD대응게시일: 2026. 10. 18.수정일: 2026. 10. 19.CNA: 416baaa9-dc9f-4396-8d5f-8c081fb06d67Received

In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix memory leak of fence event on execbuffer failure virti

위협 신호 · CVSS · EPSS · KEV

정기 패치· 높은 악용 신호 없음

CVSS

—unknown

이론적 심각도 점수

EPSS

—

예측 데이터 없음

KEV

미등재

실측 악용 기록 없음

권장 대응 기한60일 이내CISA SSVC 기준

계획된 패치 주기 내 조치(60일 이내)

외부 노출· KEV 미등재 · 자동화 어려움 · 부분 영향 · 외부 노출

CVSS 벡터 · 메트릭

CVSS 벡터 정보 없음

상세 설명

In the Linux kernel, the following vulnerability has been resolved:

drm/virtio: fix memory leak of fence event on execbuffer failure

virtio_gpu_execbuffer_ioctl() reserves a DRM event with
drm_event_reserve_init() when VIRTGPU_EXECBUF_RING_IDX selects a ring that
userspace has enabled polling for. virtio_gpu_init_submit() does this
before the BO handles, the command buffer, the syncobj arrays and the
in-fence are processed, so every later error path runs with the event
already pending, including plain argument validation failures such as an
invalid bo_handle or an in-syncobj that carries no fence.

On those paths, virtio_gpu_cleanup_submit() drops the out-fence without
cancelling the event. The fence is freed without ever having been emitted,
taking the only driver-side pointer to the event with it. Closing the DRM
file does not help. drm_events_release() unlinks pending events but
deliberately leaves the freeing to the driver's later drm_send_event(),
which never runs for an orphaned event, so the allocation is leaked
permanently.

Found when fuzzing the virtio driver with Syzkaller:

text

 1BUG: memory leak
 2unreferenced object 0xffff88802c176e80 (size 96):
 3comm "syz.1.367", pid 10561, jiffies 4294960122
 4hex dump (first 32 bytes):
 5	00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 6	c8 6e 17 2c 80 88 ff ff 00 00 00 00 00 00 00 00  .n.,............
 7backtrace (crc e1973c6b):
 8	kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
 9	slab_post_alloc_hook mm/slub.c:4597 [inline]
10	slab_alloc_node mm/slub.c:4917 [inline]
11	__kmalloc_cache_noprof+0x49d/0x6f0 mm/slub.c:5485
12	_kmalloc_noprof include/linux/slab.h:988 [inline]
13	_kzalloc_noprof include/linux/slab.h:1309 [inline]
14	virtio_gpu_fence_event_create drivers/gpu/drm/virtio/virtgpu_submit.c:282 [inline]
15	virtio_gpu_init_submit drivers/gpu/drm/virtio/virtgpu_submit.c:398 [inline]
16	virtio_gpu_execbuffer_ioctl+0xbbf/0x1aa0 drivers/gpu/drm/virtio/virtgpu_submit.c:505
17	drm_ioctl_kernel+0x1f4/0x3e0 drivers/gpu/drm/drm_ioctl.c:817
18	drm_ioctl+0x5f4/0xc70 drivers/gpu/drm/drm_ioctl.c:914
19	vfs_ioctl fs/ioctl.c:51 [inline]
20	__do_sys_ioctl fs/ioctl.c:597 [inline]
21	__se_sys_ioctl fs/ioctl.c:583 [inline]
22	__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
23	do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
24	do_syscall_64+0x116/0x800 arch/x86/entry/syscall_64.c:94
25	entry_SYSCALL_64_after_hwframe+0x77/0x7f

Fix by cancelling and freeing the DRM event on the execbuffer error path
before dropping the fence. Clear the fence's event pointer after
cancellation so it does not retain a dangling pointer.

AI 심층 분석

공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.

참고 자료 5

링크 내용 불러오는 중…