{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98509 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98509 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98509 and fix it if it is affected.\n\nWhat it is: CVE-2026-98509 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98509 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98509/ (Markdown: https://insights.sbomify.com/CVE-2026-98509/index.md)","id":"CVE-2026-98509","markdown":"https://insights.sbomify.com/CVE-2026-98509/index.md","name":"CVE-2026-98509","record":{"aliases":["AZL-109011","BELL-CVE-2026-98509","DEBIAN-CVE-2026-98509","GHSA-f38g-7gw9-c4x5","UBUNTU-CVE-2026-98509"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can trigger a memory leak in the virtio GPU driver via invalid ioctl arguments, leading to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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's 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's event pointer after\ncancellation so it does not retain a dangling pointer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/virtio: fix memory leak of fence event on execbuffer failure","id":"CVE-2026-98509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"drm/xe/vm: nuke PTs only after unlinking contested VMAs","id":"CVE-2026-98510"},"packages":[],"prev":{"headline":"drm/virtio: fix NULL pointer dereference on fence allocation failure","id":"CVE-2026-98508"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can trigger a memory leak in the virtio GPU driver via invalid ioctl arguments, leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-98509/"}