FKIE_CVE-2026-98509
Vulnerability from fkie_nvd - Published: 2026-10-18 16:17 - Updated: 2026-10-19 10:19
Severity
Summary
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:
BUG: memory leak
unreferenced object 0xffff88802c176e80 (size 96):
comm "syz.1.367", pid 10561, jiffies 4294960122
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c8 6e 17 2c 80 88 ff ff 00 00 00 00 00 00 00 00 .n.,............
backtrace (crc e1973c6b):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4597 [inline]
slab_alloc_node mm/slub.c:4917 [inline]
__kmalloc_cache_noprof+0x49d/0x6f0 mm/slub.c:5485
_kmalloc_noprof include/linux/slab.h:988 [inline]
_kzalloc_noprof include/linux/slab.h:1309 [inline]
virtio_gpu_fence_event_create drivers/gpu/drm/virtio/virtgpu_submit.c:282 [inline]
virtio_gpu_init_submit drivers/gpu/drm/virtio/virtgpu_submit.c:398 [inline]
virtio_gpu_execbuffer_ioctl+0xbbf/0x1aa0 drivers/gpu/drm/virtio/virtgpu_submit.c:505
drm_ioctl_kernel+0x1f4/0x3e0 drivers/gpu/drm/drm_ioctl.c:817
drm_ioctl+0x5f4/0xc70 drivers/gpu/drm/drm_ioctl.c:914
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x116/0x800 arch/x86/entry/syscall_64.c:94
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/virtio/virtgpu_submit.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "43bfe2b60c149bf6effda25f245a00509061fa15",
"status": "affected",
"version": "cd7f5ca33585918febe5e2f6dc090a21cfa775b0",
"versionType": "git"
},
{
"lessThan": "4e333e2336138f4659b1d7a0371c499f80428612",
"status": "affected",
"version": "cd7f5ca33585918febe5e2f6dc090a21cfa775b0",
"versionType": "git"
},
{
"lessThan": "8fa78900fd24247277c03dc7b8a2864cb12d4340",
"status": "affected",
"version": "cd7f5ca33585918febe5e2f6dc090a21cfa775b0",
"versionType": "git"
},
{
"lessThan": "ae583668f16d41fcc1b54f45848c1b6ac1d6669a",
"status": "affected",
"version": "cd7f5ca33585918febe5e2f6dc090a21cfa775b0",
"versionType": "git"
},
{
"lessThan": "b74aad23d99b279bb34d135795f39a6d8ecdc075",
"status": "affected",
"version": "cd7f5ca33585918febe5e2f6dc090a21cfa775b0",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/virtio/virtgpu_submit.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.16"
},
{
"lessThan": "5.16",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.158",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.112",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.55",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/virtio: fix memory leak of fence event on execbuffer failure\n\nvirtio_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.\n\nOn 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\u0027s later drm_send_event(),\nwhich never runs for an orphaned event, so the allocation is leaked\npermanently.\n\nFound when fuzzing the virtio driver with Syzkaller:\n\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\n\nFix by cancelling and freeing the DRM event on the execbuffer error path\nbefore dropping the fence. Clear the fence\u0027s event pointer after\ncancellation so it does not retain a dangling pointer."
}
],
"id": "CVE-2026-98509",
"lastModified": "2026-10-19T10:19:04.340",
"metrics": {},
"published": "2026-10-18T16:17:02.083",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/43bfe2b60c149bf6effda25f245a00509061fa15"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4e333e2336138f4659b1d7a0371c499f80428612"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8fa78900fd24247277c03dc7b8a2864cb12d4340"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ae583668f16d41fcc1b54f45848c1b6ac1d6669a"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/b74aad23d99b279bb34d135795f39a6d8ecdc075"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.