Strix
63.7K

CVE-2026-89816

Unknown

Last modified

CVE-2026-89816 is a vulnerability of currently unknown severity. 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..

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 24835e442f289813aa568d142a755672a740503c, < c5517b71101f61a45144e3cf77a19626355272de; >= 24835e442f289813aa568d142a755672a740503c, < 866a04137dac7e82a3848851061ff7ed15c2847e; >= 24835e442f289813aa568d142a755672a740503c, < 6a6a7aae4681a20cd32789fea9a487aaafa0e7a3; >= 24835e442f289813aa568d142a755672a740503c, < e2f27b5ed9084feb7bae9ef2bc80de37c92280b1; >= 24835e442f289813aa568d142a755672a740503c, < ff73f5f43d032c3da3c534c517f661e8dfeb358a; >= 24835e442f289813aa568d142a755672a740503c, < 66b1b309886337745d395bbc158440ab196305ce; >= 24835e442f289813aa568d142a755672a740503c, < e6195b941fdc8d81fc431c9f25539cf6c6234b51; >= 24835e442f289813aa568d142a755672a740503c, < 4d4be202165e832d74849b4a68e289a2a377039c; c75fe7899538890109aad7bbf92b2f304389e825; 2a3241044b1c4ecc13f73b7158881881fb7534a1; >= 4.9.19, < 4.10; >= 4.10.7, < 4.11
LinuxLinux4.11

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-89816?
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.
How severe is CVE-2026-89816?
Severity scoring for CVE-2026-89816 is pending analysis.
How do I fix CVE-2026-89816?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-89816?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST