CVE-2026-89816 — drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 24835e442f289813aa568d142a755672a740503c and < c5517b71101f61a45144e3cf77a19626355272de≥ 24835e442f289813aa568d142a755672a740503c and < 866a04137dac7e82a3848851061ff7ed15c2847e≥ 24835e442f289813aa568d142a755672a740503c and < 6a6a7aae4681a20cd32789fea9a487aaafa0e7a3≥ 24835e442f289813aa568d142a755672a740503c and < e2f27b5ed9084feb7bae9ef2bc80de37c92280b1≥ 24835e442f289813aa568d142a755672a740503c and < ff73f5f43d032c3da3c534c517f661e8dfeb358a≥ 24835e442f289813aa568d142a755672a740503c and < 66b1b309886337745d395bbc158440ab196305ce≥ 24835e442f289813aa568d142a755672a740503c and < e6195b941fdc8d81fc431c9f25539cf6c6234b51≥ 24835e442f289813aa568d142a755672a740503c and < 4d4be202165e832d74849b4a68e289a2a377039c and 5 moreversion c75fe7899538890109aad7bbf92b2f304389e825version 2a3241044b1c4ecc13f73b7158881881fb7534a1≥ 4.9.19 and < 4.10≥ 4.10.7 and < 4.11version 4.11 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 22, 2026 · 7 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/66b1b309886337745d395bbc158440ab196305ce
- git.kernel.org/stable/c/e2f27b5ed9084feb7bae9ef2bc80de37c92280b1
- git.kernel.org/stable/c/4d4be202165e832d74849b4a68e289a2a377039c
- github.com/advisories/GHSA-6f96-mhg4-cfw6
- git.kernel.org/stable/c/866a04137dac7e82a3848851061ff7ed15c2847e
- nvd.nist.gov/vuln/detail/CVE-2026-89816
- git.kernel.org/stable/c/6a6a7aae4681a20cd32789fea9a487aaafa0e7a3
- git.kernel.org/stable/c/ff73f5f43d032c3da3c534c517f661e8dfeb358a
- git.kernel.org/stable/c/e6195b941fdc8d81fc431c9f25539cf6c6234b51
- git.kernel.org/stable/c/c5517b71101f61a45144e3cf77a19626355272de
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98869 bpf: Infer zext_dst based on static register liveness analysis 1d
- Unknown CVE-2023-7356 Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID 1d
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 4d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 4d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 4d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 4d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89816 is "drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.