CVE-2026-98319: Linux kernel · drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:27 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr When an out_fence_ptr is provided but DRM_MODE_PAGE_FLIP_EVENT is not set, a drm_pending_vblank_event will be allocated. If later, there is an allocation failure or another failure at setup_out_fence(), that event will not have base.fence set and it will not be released at complete_signaling(). Release the event and set crtc_state->event to NULL just like in the DRM_MODE_PAGE_FLIP_EVENT case when there is a failure at drm_event_reserve_init(). That is, prepare_signaling() releases the event and there is nothing to be done at complete_signaling(). Use drm_event_cancel_free() as that will also undo drm_event_reserve_init() in case it has been called.
References
- ubuntu.com/security/CVE-2026-98319 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98319 (opens in a new tab)
- git.kernel.org/linus/9eb1a393c89a79c4210230d23e7d88d239c61d7b (opens in a new tab)
- git.kernel.org/stable/c/3d6576ed3de01e8a378397b7020e33ae3d40aa6c (opens in a new tab)
- git.kernel.org/stable/c/780716e2e019186fa6e5aad097a44b87b0b5388f (opens in a new tab)
- git.kernel.org/stable/c/86c33f740aa27e9cdc1259f0cc59c9c58f545e4b (opens in a new tab)
- git.kernel.org/stable/c/88c450e23b8fd4f1dcd329562f5e81ef05f3d941 (opens in a new tab)
- git.kernel.org/stable/c/9eb1a393c89a79c4210230d23e7d88d239c61d7b (opens in a new tab)
- git.kernel.org/stable/c/b9a68a9ccaada15d8dd0102c188cc6b868ff800b (opens in a new tab)
- git.kernel.org/stable/c/d0be0516b5224eb5b6f42f8564a8deadb20ae16b (opens in a new tab)
- git.kernel.org/stable/c/daefd7ff159b0d1fb8c9e64430dcbe2aca1bdd09 (opens in a new tab)