fbdev: uvesafb: unregister connector callback on init failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 8bdb3a2d7df48b861972c4bfb58490853a228f51 · < 466a8af0dee2cf745307155e26884e19a37b7e15| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fbdev: uvesafb: unregister connector callback on init failure
uvesafb_init() registers the v86d connector callback before registering the platform driver. If platform_driver_register() fails, the function returns the error directly and leaves the connector callback registered.
The later platform-device failure path already unregisters the callback. Add the same cleanup before the final return when platform-driver registration fails.
This issue was identified during our ongoing static-analysis research while reviewing kernel code.
From the CVE record · Linux
The Linux kernel’s uvesafb initialization leaves a v86d connector callback registered if platform-driver registration fails. The input does not establish how an attacker could trigger or exploit this condition, or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with uvesafb should check their installations; affected versions were not provided.