CVE-2026-98319

drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr

Published Oct 6, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

In the Linux kernel’s Direct Rendering Manager, a memory leak occurs when an out_fence_ptr is supplied without the DRM_MODE_PAGE_FLIP_EVENT flag. The kernel allocates a drm_pending_vblank_event, but if a subsequent allocation or setup failure occurs, the event is not freed, causing persistent kernel memory exhaustion. This flaw is a resource‑management defect that can degrade system stability over time and may lead to a denial‑of‑service condition, but it does not provide direct remote code execution or privilege escalation.

Affected Systems

All Linux kernel builds before the resolution commit are affected wherever DRM devices are exposed. Systems running the kernel on hardware that supports DRM should assess whether they could trigger page‑flip operations that use out_fence_ptrs. No specific version numbers are enumerated, so any kernel version preceding the commit identified in the CVE’s background commits is considered vulnerable.

Risk and Exploitability

The CVSS score is 5.5 and the EPSS score is < 1% (approximately 0.00184), indicating a very low exploitation probability. The vulnerability is not listed in CISA KEV, so no known widespread exploitation is reported. The likely attack vector is local exploitation by a user or application with DRM access; triggering page‑flip events that fail with an out_fence_ptr can exhaust kernel memory. The impact remains limited to memory resource exhaustion and potential service interruption, but requires sufficient privilege to invoke DRM operations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to the most recent version that includes the commit fixing the drm_pending_vblank_event leak; this patch releases the event and clears crtc_state.
  • After the kernel update, restart the display server (Xorg, Wayland, etc.) or reboot to load the updated DRM code.
  • Configure applications to use page‑flip events only with valid fence pointers and the DRM_MODE_PAGE_FLIP_EVENT flag, or disable page‑flip events if they are unnecessary, to prevent the error path that triggers the memory leak.

Generated by OpenCVE AI on October 11, 2026 at 06:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4841-1 linux security update
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6568-1 linux security update
Ubuntu USN Ubuntu USN USN-8961-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9022-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9023-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9029-1 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-9039-1 Linux kernel (Azure CVM) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9183-1 Linux kernel (FIPS) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-401
CWE-459
Type Values Removed Values Added
Weaknesses CWE-772
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low

Type Values Removed Values Added
Weaknesses CWE-401
CWE-459
Type Values Removed Values Added
Weaknesses CWE-401
CWE-459
Type Values Removed Values Added
Weaknesses CWE-401
CWE-459
Type Values Removed Values Added
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.
Title drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 9:17 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 6, 2026, 9:18 AM
Modified
Oct 19, 2026, 10:18 AM
Severity
Low
Public date
Oct 6, 2026, 12:00 AM