FKIE_CVE-2026-98609
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 object leak when drm_gem_handle_create() fails
virtio_gpu_gem_create() owns the reference taken by
virtio_gpu_object_create(). On the drm_gem_handle_create() error path it
calls drm_gem_object_release() instead of dropping that reference.
drm_gem_object_release() is the inverse of drm_gem_object_init() and does
not touch the reference count or call obj->funcs->free(), so it is only
correct as the last step of a destructor, as in
virtio_gpu_cleanup_object(). Using it here leaves the bo at refcount 1
with no remaining reference, so virtio_gpu_free_object() never runs and
the shmem pages, sg table and virtio_gpu_object are leaked. Since
virtio_gpu_object_create() has already set bo->created,
VIRTIO_GPU_CMD_RESOURCE_UNREF is not queued either, leaking the host-side
resource and the resource id.
drm_gem_handle_create_tail() drops the handle reference on all of its
internal error paths, so the caller only has to drop its own. Use
drm_gem_object_put(), matching the success path below.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/virtio/virtgpu_gem.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "13423a058187c2039aa8cb235c916be4477221b7",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "264ae8ac8fd625b6c118baf16c111adeee2ec632",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "e2edd2d78d2cf8446de017adec9598feefed3297",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "372e9c3d45f664a2c000427ccbf6cdc2f99b3170",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "a93dce15dfef200c346b050a2acbed516cc62706",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "f75066c79d1eec453c0d386ef8636873d1e11f2c",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
},
{
"lessThan": "36570ef2244cc4d7563b1f0157bc0f032498638c",
"status": "affected",
"version": "dc5698e80cf724770283e10414054662bdf6ccfa",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/virtio/virtgpu_gem.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.2"
},
{
"lessThan": "4.2",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.271",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.222",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.189",
"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 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."
}
],
"id": "CVE-2026-98609",
"lastModified": "2026-10-19T10:19:22.927",
"metrics": {},
"published": "2026-10-18T16:17:13.677",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/13423a058187c2039aa8cb235c916be4477221b7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/264ae8ac8fd625b6c118baf16c111adeee2ec632"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/36570ef2244cc4d7563b1f0157bc0f032498638c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/372e9c3d45f664a2c000427ccbf6cdc2f99b3170"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a93dce15dfef200c346b050a2acbed516cc62706"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e2edd2d78d2cf8446de017adec9598feefed3297"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f75066c79d1eec453c0d386ef8636873d1e11f2c"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
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.
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.
Loading…