{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98609 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98609 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-98609 and fix it if it is affected.\n\nWhat it is: CVE-2026-98609 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-98609 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-98609/ (Markdown: https://insights.sbomify.com/CVE-2026-98609/index.md)","id":"CVE-2026-98609","markdown":"https://insights.sbomify.com/CVE-2026-98609/index.md","name":"CVE-2026-98609","record":{"aliases":["AZL-109370","BELL-CVE-2026-98609","DEBIAN-CVE-2026-98609","GHSA-4mj5-5wcx-f4jj","UBUNTU-CVE-2026-98609"],"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, 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 object leak when drm_gem_handle_create() fails\n\nvirtio_gpu_gem_create() owns the reference taken by\nvirtio_gpu_object_create(). On the drm_gem_handle_create() error path it\ncalls drm_gem_object_release() instead of dropping that reference.\n\ndrm_gem_object_release() is the inverse of drm_gem_object_init() and does\nnot touch the reference count or call obj-\u003efuncs-\u003efree(), so it is only\ncorrect as the last step of a destructor, as in\nvirtio_gpu_cleanup_object(). Using it here leaves the bo at refcount 1\nwith no remaining reference, so virtio_gpu_free_object() never runs and\nthe shmem pages, sg table and virtio_gpu_object are leaked. Since\nvirtio_gpu_object_create() has already set bo-\u003ecreated,\nVIRTIO_GPU_CMD_RESOURCE_UNREF is not queued either, leaking the host-side\nresource and the resource id.\n\ndrm_gem_handle_create_tail() drops the handle reference on all of its\ninternal error paths, so the caller only has to drop its own. Use\ndrm_gem_object_put(), matching the success path below.","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 object leak when drm_gem_handle_create() fails","id":"CVE-2026-98609","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net/sched: sch_hfsc: bound the classify inner-filter walk with a drift budget","id":"CVE-2026-98610"},"packages":[],"prev":{"headline":"drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl()","id":"CVE-2026-98608"},"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, leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-98609/"}