Heimdall Security Logo

CVE-2026-98609

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
Linux•Linux•Versions : <f75066c79d1eec453c0d386ef8636873d1e11f2c, <e2edd2d78d2cf8446de017adec9598feefed3297, <=6.1.*, <=6.12.*, <4.2, <36570ef2244cc4d7563b1f0157bc0f032498638c, <a93dce15dfef200c346b050a2acbed516cc62706, 6.18.55, 0, 6.12.112, 5.10.271, 6.6.158, <264ae8ac8fd625b6c118baf16c111adeee2ec632, <=5.10.*, <=6.6.*, 6.1.189, <13423a058187c2039aa8cb235c916be4477221b7, <=6.18.*, 5.15.222, dc5698e80cf724770283e10414054662bdf6ccfa, <=7.2.*, 4.2, 7.2.9, <=*, <372e9c3d45f664a2c000427ccbf6cdc2f99b3170, <=5.15.*, <687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc, 7.3

Description

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.

Gravité et risque d'exploitation

CVE-2026-98609 obtient un score CVSS de 0.0/10, soit une gravité non évaluée.

Que faire ?

  • Vérifiez si Linux (versions <f75066c79d1eec453c0d386ef8636873d1e11f2c, <e2edd2d78d2cf8446de017adec9598feefed3297, <=6.1.*, <=6.12.*, <4.2, <36570ef2244cc4d7563b1f0157bc0f032498638c, <a93dce15dfef200c346b050a2acbed516cc62706, 6.18.55, 0, 6.12.112, 5.10.271, 6.6.158, <264ae8ac8fd625b6c118baf16c111adeee2ec632, <=5.10.*, <=6.6.*, 6.1.189, <13423a058187c2039aa8cb235c916be4477221b7, <=6.18.*, 5.15.222, dc5698e80cf724770283e10414054662bdf6ccfa, <=7.2.*, 4.2, 7.2.9, <=*, <372e9c3d45f664a2c000427ccbf6cdc2f99b3170, <=5.15.*, <687be2f8b5e0e0ca9a7028f8f6413d0ed3fbb9dc, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE