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.
Metrics
Affected Vendors & Products
References
History
Fri, 23 May 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-401 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Wed, 02 Apr 2025 14:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Tue, 01 Apr 2025 16:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | drm/hyperv: Fix address space leak when Hyper-V DRM device is removed | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-04-01T15:47:08.168Z
Updated: 2025-05-04T07:26:27.998Z
Reserved: 2024-12-29T08:45:45.798Z
Link: CVE-2025-21978

No data.

Status : Awaiting Analysis
Published: 2025-04-01T16:15:29.183
Modified: 2025-04-01T20:26:01.990
Link: CVE-2025-21978
