The vulnerability arises when the kernel drops references to CRTC color blobs but fails to clear the corresponding pointers. If the same hardware state is subsequently cleaned up, the code attempts to drop the identical references again, which can lead to double free or use‑after‑free errors. The result is a crash or undefined behavior in the DRM subsystem, effectively causing a denial of service or kernel instability. The weakness is a memory‑management flaw, specifically a use‑after‑free scenario.

The affected product is the Linux kernel; no specific kernel version information is provided in the CVE data, so any release that lacks the commit that clears the pointers is potentially vulnerable.

The CVSS score and EPSS data are not available, and the vulnerability is not listed in CISA KEV, which indicates that no public exploitation has been reported. The risk is localized to systems running a kernel that has not been patched with this fix. An attacker would need some method to trigger repeated CRTC state cleanup – for example, by driving the DRM subsystem into a failure path – so the immediate threat level to unprivileged users is low. Nevertheless, the flaw can cause kernel crashes, which is a serious reliability issue.