CVE-2026-89816

drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used

N/A
Published: September 16, 2026 at 10:30 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

24835e442f289813aa568d142a755672a740503c2a3241044b1c4ecc13f73b7158881881fb7534a14.10.74.114.9.19c75fe7899538890109aad7bbf92b2f304389e825
Vendor states this is fixed in 4d4be202165e832d74849b4a68e289a2a377039c (fixed)
Vendor states this is fixed in 66b1b309886337745d395bbc158440ab196305ce (fixed)
Vendor states this is fixed in 6a6a7aae4681a20cd32789fea9a487aaafa0e7a3 (fixed)
Vendor states this is fixed in 866a04137dac7e82a3848851061ff7ed15c2847e (fixed)
Vendor states this is fixed in c5517b71101f61a45144e3cf77a19626355272de (fixed)
Vendor states this is fixed in e2f27b5ed9084feb7bae9ef2bc80de37c92280b1 (fixed)
Vendor states this is fixed in e6195b941fdc8d81fc431c9f25539cf6c6234b51 (fixed)
Vendor states this is fixed in ff73f5f43d032c3da3c534c517f661e8dfeb358a (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card