The driver for MediaTek DRM, mtk_drm_bind(), faultlessly takes a reference to the disp‑mutex device via of_find_device_by_node() when binding non‑master hardware but never releases that reference before returning. This omission creates a reference leak that can accumulate over time, depleting kernel reference‑count resources and potentially destabilizing the system. The vulnerability does not provide direct control over the kernel, but the long‑term leakage of kernel objects can degrade overall system stability.

Any Linux kernel build that incorporates the drm/mediatek DRM driver before the patch identified in commit 3753e34b is affected. No specific kernel versions are enumerated in the advisory, so the issue applies broadly to all builds that include the unpatched code path for non‑master device bindings.

The CVSS score of 2.3 indicates a low severity, and the EPSS score of less than 1% signals a very low probability of exploitation. The vulnerability is not listed in CISA's KEV catalog. The likely attack vector is inferred: an attacker who can repeatedly trigger bindings of non‑master devices within the kernel, which requires local kernel privilege or the ability to reload the module. No public exploitation evidence is reported, so the immediate risk remains low but the residual resource leak presents a potential long‑term risk if the cache reaches saturation.