Linux Kernel up to 7.3-rc1 drm drm/ complete_signaling memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$0-$5k0.00+

Summaryinfo

A vulnerability classified as problematic has been found in Linux Kernel up to 7.3-rc1. Affected is the function complete_signaling of the file drm/ of the component drm. The manipulation leads to memory leak. This vulnerability is referenced as CVE-2026-89816. The attack can only be performed from a local environment. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.3-rc1 and classified as problematic. This issue affects the function complete_signaling of the file drm/ of the component drm. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-89816 since 09/11/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5 or 7.3-rc2 eliminates this vulnerability. Applying the patch c5517b71101f61a45144e3cf77a19626355272de/866a04137dac7e82a3848851061ff7ed15c2847e/6a6a7aae4681a20cd32789fea9a487aaafa0e7a3/e2f27b5ed9084feb7bae9ef2bc80de37c92280b1/ff73f5f43d032c3da3c534c517f661e8dfeb358a/66b1b309886337745d395bbc158440ab196305ce/e6195b941fdc8d81fc431c9f25539cf6c6234b51/4d4be202165e832d74849b4a68e289a2a377039c is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.270/5.15.221/6.1.188/6.6.157/6.12.110/6.18.51/7.2.5/7.3-rc2
Patch: c5517b71101f61a45144e3cf77a19626355272de/866a04137dac7e82a3848851061ff7ed15c2847e/6a6a7aae4681a20cd32789fea9a487aaafa0e7a3/e2f27b5ed9084feb7bae9ef2bc80de37c92280b1/ff73f5f43d032c3da3c534c517f661e8dfeb358a/66b1b309886337745d395bbc158440ab196305ce/e6195b941fdc8d81fc431c9f25539cf6c6234b51/4d4be202165e832d74849b4a68e289a2a377039c

Timelineinfo

09/11/2026 CVE reserved
09/16/2026 +5 days Advisory disclosed
09/16/2026 +0 days VulDB entry created
09/16/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-89816 (🔒)
GCVE (CVE): GCVE-0-2026-89816
GCVE (VulDB): GCVE-100-405635

Entryinfo

Created: 09/16/2026 13:08
Changes: 09/16/2026 13:08 (60)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!