The vulnerability arises when the DRM framebuffer helper does not defer mode‑set configuration if fbdev_probe() fails with an error other than -EAGAIN. This omission leaves underlying mode sets with valid modes and connectors but no associated framebuffer, and the helper is not marked for retry. Subsequent restore operations commit the stale configuration, triggering a kernel warning about a missing framebuffer pointer. The flaw is a lack of proper error handling for probe failures.

All Linux kernel builds that include the unpatched DRM framebuffer helper code are potentially impacted. The available information does not specify a version range, so any kernel version prior to the commit that introduced the defer‑setup change is vulnerable.

The CVSS score of 4.7 and an EPSS score of less than 1% indicate a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. Because the defect is confined to kernel mode and requires a probe failure during driver initialization, it is unlikely to be exploitable remotely; local or privileged access that triggers the probe failure would be necessary. The primary risk is to kernel stability, manifested by unexpected warnings and potential unstable driver behavior, rather than classic attack objectives such as code execution or data exfiltration. The likely attack vector is local or privileged (inferred).