CVE-2026-98509: Linux kernel · drm/virtio: fix memory leak of fence event on execbuffer failure
Source GCVE Database
Not known to be exploited · fixed in b74aad23d99b279bb34d135795f39a6d8ecdc075 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 16:00 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b74aad23d99b279bb34d135795f39a6d8ecdc075, ae583668f16d41fcc1b54f45848c1b6ac1d6669a, 43bfe2b60c149bf6effda25f245a00509061fa15 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available that cancels and frees the DRM event on execbuffer failure paths and clears the fence's event pointer to prevent leaks. Users should update their Linux kernel to a version that includes this fix. Since this is a kernel-level issue, applying the official kernel patch or upgrading to a fixed kernel release is the recommended remediation.
Description
A memory leak vulnerability in the Linux kernel's drm/virtio driver was fixed. The issue occurs when an execbuffer operation fails, leaving a DRM fence event allocated but never freed, causing a permanent memory leak. This happens because the event is reserved early but not cancelled on error paths, and the driver loses the pointer to free it. The flaw was discovered via fuzzing with Syzkaller and affects the virtio_gpu_execbuffer_ioctl() function.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98509 (opens in a new tab)
- git.kernel.org/stable/c/43bfe2b60c149bf6effda25f245a00509061fa15 (opens in a new tab)
- git.kernel.org/stable/c/4e333e2336138f4659b1d7a0371c499f80428612 (opens in a new tab)
- git.kernel.org/stable/c/8fa78900fd24247277c03dc7b8a2864cb12d4340 (opens in a new tab)
- git.kernel.org/stable/c/ae583668f16d41fcc1b54f45848c1b6ac1d6669a (opens in a new tab)
- git.kernel.org/stable/c/b74aad23d99b279bb34d135795f39a6d8ecdc075 (opens in a new tab)