GHSA-9VQ3-MXMP-FQ54
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
drm/virtio: release the GEM object on virtio_gpu_vram_create() errors
virtio_gpu_vram_create() frees the object with a bare kfree(vram) on both error paths after drm_gem_private_object_init() has run, and on the second one after drm_gem_create_mmap_offset() has linked obj->vma_node into the device's VMA offset manager. The freed object stays in that interval tree, so a later lookup or insertion walks freed memory, and the dma_resv and gpuva lock are never destroyed.
Call drm_gem_object_release() before kfree() on both paths.
{
"affected": [],
"aliases": [
"CVE-2026-98606"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:13Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/virtio: release the GEM object on virtio_gpu_vram_create() errors\n\nvirtio_gpu_vram_create() frees the object with a bare kfree(vram) on\nboth error paths after drm_gem_private_object_init() has run, and on the\nsecond one after drm_gem_create_mmap_offset() has linked obj-\u003evma_node\ninto the device\u0027s VMA offset manager. The freed object stays in that\ninterval tree, so a later lookup or insertion walks freed memory, and\nthe dma_resv and gpuva lock are never destroyed.\n\nCall drm_gem_object_release() before kfree() on both paths.",
"id": "GHSA-9vq3-mxmp-fq54",
"modified": "2026-10-18T18:31:56Z",
"published": "2026-10-18T18:31:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98606"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/036d28db1818af2f9d80db771f5405da84d7732d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/03bdbf182082694ab2add620d85f1a8b8f51bbbc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5118b5fdf1eb9922a0cdd2afd25252081e2d4302"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5c2cb3dd1447752b73d4f44d6b7434bc5259bfec"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7c8deb77d05bcc8f79e255f669d82ec6ce91be12"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/977c2934064969503cabf98b1135d202ff62822e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a9bb8f8fd5694185c2f71ff91869afb300aab392"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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…
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.
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.