drm/hyperv: Fix address space leak when Hyper-V DRM device is removed
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/hyperv: Fix address space leak when Hyper-V DRM device is removed
When a Hyper-V DRM device is probed, the driver allocates MMIO space for the vram, and maps it cacheable. If the device removed, or in the error path for device probing, the MMIO space is released but no unmap is done. Consequently the kernel address space for the mapping is leaked.
Fix this by adding iounmap() calls in the device removal path, and in the error path during device probing.
From the CVE record · Linux
The Linux kernel’s Hyper-V DRM driver can leak kernel address space allocated for a VRAM mapping when a device is removed or probing fails. The input does not describe an attacker action, authentication requirement, or user interaction needed to trigger these conditions.
Engineers running Linux kernels with the Hyper-V DRM driver should check their kernel versions; affected versions are not specified.