0.0
NA
CVE-2026-89816
drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used
Description

In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used Commit 1c6ceeee6ebb ("drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits") fixed a very similar issue when the event was allocated by drm_atomic_helper_setup_commit() itself. However, if the event is allocated in prepare_signaling(), it will also be set to NULL in complete_signaling(), which prevents drm_crtc_commit from being put in __drm_atomic_helper_crtc_destroy_state(). Dropping the reference when the event is set to NULL at complete_signaling() fixes the leak. The leak can be reproduced by sending a signal to the thread using DRM_MODE_PAGE_FLIP_EVENT and using a sw_sync fence to cause the atomic ioctl to block at drm_atomic_helper_wait_for_fences(). It happened both with amdgpu and vkms.

INFO

Published Date :

Sept. 16, 2026, 11:16 a.m.

Last Modified :

Sept. 16, 2026, 11:16 a.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-89816 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Fix memory leak in the Linux kernel's Direct Rendering Manager component.
  • Apply the kernel commit that fixes the drm_crtc_commit leak.
  • Update the Linux kernel to the patched version.
  • Ensure proper reference counting for events in DRM.
  • Test the fix for DRM event allocation and signaling.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-89816 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-89816 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-89816 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-89816 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Sep. 16, 2026

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used Commit 1c6ceeee6ebb ("drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits") fixed a very similar issue when the event was allocated by drm_atomic_helper_setup_commit() itself. However, if the event is allocated in prepare_signaling(), it will also be set to NULL in complete_signaling(), which prevents drm_crtc_commit from being put in __drm_atomic_helper_crtc_destroy_state(). Dropping the reference when the event is set to NULL at complete_signaling() fixes the leak. The leak can be reproduced by sending a signal to the thread using DRM_MODE_PAGE_FLIP_EVENT and using a sw_sync fence to cause the atomic ioctl to block at drm_atomic_helper_wait_for_fences(). It happened both with amdgpu and vkms.
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/89xxx/CVE-2026-89816.json">CVE-2026-89816</a>
    Added Reference https://git.kernel.org/stable/c/4d4be202165e832d74849b4a68e289a2a377039c
    Added Reference https://git.kernel.org/stable/c/66b1b309886337745d395bbc158440ab196305ce
    Added Reference https://git.kernel.org/stable/c/6a6a7aae4681a20cd32789fea9a487aaafa0e7a3
    Added Reference https://git.kernel.org/stable/c/866a04137dac7e82a3848851061ff7ed15c2847e
    Added Reference https://git.kernel.org/stable/c/c5517b71101f61a45144e3cf77a19626355272de
    Added Reference https://git.kernel.org/stable/c/e2f27b5ed9084feb7bae9ef2bc80de37c92280b1
    Added Reference https://git.kernel.org/stable/c/e6195b941fdc8d81fc431c9f25539cf6c6234b51
    Added Reference https://git.kernel.org/stable/c/ff73f5f43d032c3da3c534c517f661e8dfeb358a
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.