The uvesafb framebuffer driver registers a v86d connector callback during initialization before attempting to register its platform driver. If the platform registration fails, the callback remains registered, and a later failure path fails to remove it. The orphaned callback can be invoked later by the kernel, leading to an Oops or kernel crash. This flaw causes reliability issues and may result in system reboot, but it does not provide code execution or privilege escalation.

Any configuration of the Linux kernel that includes the uvesafb driver is potentially affected. The CVE entry does not list specific kernel versions, so any kernel that still contains the legacy uvesafb implementation prior to the regression fix is at risk.

The CVSS score of 2.3 reflects a low severity assessment. The EPSS score of < 1% and the flaw is not in the CISA KEV catalog. Exploitation requires the kernel to load a uvesafb driver and for platform_driver_register() to fail—a scenario unlikely under normal operation. Overall risk is modest, primarily limited to local environments where such initialization failures might occur.