drm/virtio: Fix driver removal with disabled KMS
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/virtio: Fix driver removal with disabled KMS
DRM atomic and modesetting aren't initialized if virtio-gpu driver built with disabled KMS, leading to access of uninitialized data on driver removal/unbinding and crashing kernel. Fix it by skipping shutting down atomic core with unavailable KMS.
From the CVE record · Linux
The virtio-gpu driver can access uninitialized data when it is built with KMS disabled and then removed or unbound, crashing the kernel. The input does not establish whether an attacker can trigger removal or what access they would need.
Engineers running Linux kernels with the virtio-gpu driver built with KMS disabled should check whether their kernel is affected; affected versions are not specified.