GHSA-4MJ5-5WCX-F4JJ

Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31
VLAI
Details

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.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-98609"
  ],
  "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: 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": "GHSA-4mj5-5wcx-f4jj",
  "modified": "2026-10-18T18:31:56Z",
  "published": "2026-10-18T18:31:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98609"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/13423a058187c2039aa8cb235c916be4477221b7"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/264ae8ac8fd625b6c118baf16c111adeee2ec632"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/36570ef2244cc4d7563b1f0157bc0f032498638c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/372e9c3d45f664a2c000427ccbf6cdc2f99b3170"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a93dce15dfef200c346b050a2acbed516cc62706"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e2edd2d78d2cf8446de017adec9598feefed3297"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f75066c79d1eec453c0d386ef8636873d1e11f2c"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

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

JSON

Loading timeline…




    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.