Skip to main content
VulnerabilityPublished

CVE-2026-98608: Linux kernel · drm/virtio: fix object leak in virtio_gpu_resource_create_ioctl()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d33d5ef8225538f76e4598c09e2074834667bb8d : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d33d5ef8225538f76e4598c09e2074834667bb8d, b516446a25bf365cfffe3d7884ea6637f7f70862, 1586ee6107acab3b14510ac6af939f1253269df8 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257, < d33d5ef8225538f76e4598c09e2074834667bb8d
Fixed in
  • d33d5ef8225538f76e4598c09e2074834667bb8d
LinuxLinuxAffected
  • ≥ 62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257, < b516446a25bf365cfffe3d7884ea6637f7f70862
Fixed in
  • b516446a25bf365cfffe3d7884ea6637f7f70862
LinuxLinuxAffected
  • ≥ 62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257, < 1586ee6107acab3b14510ac6af939f1253269df8
Fixed in
  • 1586ee6107acab3b14510ac6af939f1253269df8
LinuxLinuxAffected
  • ≥ 62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257, < 749d8bb964b3414ef967d5ec80f2f1b5b3a510d9
Fixed in
  • 749d8bb964b3414ef967d5ec80f2f1b5b3a510d9
LinuxLinuxAffected
  • ≥ 62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257, < 574ae9fa5fd3658bee23cb544fe5a0d1d750016a
Fixed in
  • 574ae9fa5fd3658bee23cb544fe5a0d1d750016a
LinuxLinuxAffected
  • ≥ 62fb7a5e10962ac6ae2a2d2dbd3aedcb2a3e3257, < 477bc3068fc3777b9d8ffd79e265b0dfdf2d3a6b
Fixed in
  • 477bc3068fc3777b9d8ffd79e265b0dfdf2d3a6b

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and has been applied in the Linux kernel versions identified by the provided commit hashes. Users and administrators should update to these fixed versions to remediate the vulnerability. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's drm/virtio component caused an object leak in the virtio_gpu_resource_create_ioctl() function. The issue arises because drm_gem_object_release() is called incorrectly on an error path, preventing the proper freeing of resources. This leads to leaks of the virtio_gpu_object, its associated pages, scatter-gather table, resource ID, and host-side resource. The flaw has been fixed by replacing drm_gem_object_release() with drm_gem_object_put().

References

Community reviews

Loading reviews…