CVE-2026-89816: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 4.10, 4.11, 4d4be202165e832d74849b4a68e289a2a377039c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 4.10, 4.11, 4d4be202165e832d74849b4a68e289a2a377039c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- c75fe7899538890109aad7bbf92b2f304389e825, 2a3241044b1c4ecc13f73b7158881881fb7534a1, 4.11affected
- 24835e442f289813aa568d142a755672a740503c and later · before c5517b71101f61a45144e3cf77a19626355272deaffected · git
- 24835e442f289813aa568d142a755672a740503c and later · before 866a04137dac7e82a3848851061ff7ed15c2847eaffected · git
- 24835e442f289813aa568d142a755672a740503c and later · before 6a6a7aae4681a20cd32789fea9a487aaafa0e7a3affected · git
- 24835e442f289813aa568d142a755672a740503c and later · before e2f27b5ed9084feb7bae9ef2bc80de37c92280b1affected · git
- 24835e442f289813aa568d142a755672a740503c and later · before ff73f5f43d032c3da3c534c517f661e8dfeb358aaffected · git
- 24835e442f289813aa568d142a755672a740503c and later · before 66b1b309886337745d395bbc158440ab196305ceaffected · git
- 24835e442f289813aa568d142a755672a740503c and later · before e6195b941fdc8d81fc431c9f25539cf6c6234b51affected · git
- 24835e442f289813aa568d142a755672a740503c and later · before 4d4be202165e832d74849b4a68e289a2a377039caffected · git
- 4.9.19 and later · before 4.10affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89814Sep 16, 2026 · drm/amdgpu: clamp the isolation index for rings outside a partition31Monitor
- ← EarlierCVE-2026-89815Sep 16, 2026 · drm/ttm: Drop tt->restore after successful restore31Monitor
- Later →CVE-2026-89817Sep 16, 2026 · drm/gud: NUL-terminate TV mode names read from the device0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.11 | Vendor (CNA) |
| Linux Linux | 4d4be202165e832d74849b4a68e289a2a377039c | Vendor (CNA) |
| Linux Linux | 66b1b309886337745d395bbc158440ab196305ce | Vendor (CNA) |
| Linux Linux | 6a6a7aae4681a20cd32789fea9a487aaafa0e7a3 | Vendor (CNA) |
| Linux Linux | 866a04137dac7e82a3848851061ff7ed15c2847e | Vendor (CNA) |
| Linux Linux | c5517b71101f61a45144e3cf77a19626355272de | Vendor (CNA) |
| Linux Linux | e2f27b5ed9084feb7bae9ef2bc80de37c92280b1 | Vendor (CNA) |
| Linux Linux | e6195b941fdc8d81fc431c9f25539cf6c6234b51 | Vendor (CNA) |
| Linux Linux | ff73f5f43d032c3da3c534c517f661e8dfeb358a | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/66b1b309886337745d395bbc158440ab196305ce
- git.kernel.org/stable/c/6a6a7aae4681a20cd32789fea9a487aaafa0e7a3
- git.kernel.org/stable/c/866a04137dac7e82a3848851061ff7ed15c2847e
- git.kernel.org/stable/c/c5517b71101f61a45144e3cf77a19626355272de
- git.kernel.org/stable/c/e2f27b5ed9084feb7bae9ef2bc80de37c92280b1
- git.kernel.org/stable/c/e6195b941fdc8d81fc431c9f25539cf6c6234b51
- git.kernel.org/stable/c/ff73f5f43d032c3da3c534c517f661e8dfeb358a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.