When the AMD DRM display driver performs a skip_modeset path, it releases the new_stream object but does not set the pointer to NULL. If a later error triggers the fail label, the same dangling pointer is released again, producing a double free that can corrupt kernel memory. This double free constitutes a use‑after‑free flaw and can lead to crashes or, in a kernel context, potential privilege escalation. The weakness is a classic example of unchecked release after use (CWE‑416).

All Linux kernel builds that include the AMD DRM display code are affected, as indicated by the vendor list of "Linux:Linux". No specific product versions are disclosed; therefore any installation that has not incorporated the patch from commit 99f3af1 remains vulnerable.

There is no EPSS value and the vulnerability is not listed in the CISA KEV catalog, but the absence of an exploit score does not reduce its inherent danger. The flaw requires interaction with the graphics subsystem and can be triggered by user‑space applications that interface with DRM. A local user, or potentially a remote attacker who can run user‑space code, could exploit the double free to corrupt kernel memory, leading to denial of service or privilege escalation. With no publicly known exploit and limited visibility in threat feeds, the current risk is moderate yet unacceptably high for kernel code.