CVE-2025-21978
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.
Does this matter?
Lower severity and a low EPSS score (0.19%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.19% probability · 9th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-401
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/158242b56bf465a73e1edeac0fe828a8acad4499Patch
- https://git.kernel.org/stable/c/24f1bbfb2be77dad82489c1468bbb14312aab129Patch
- https://git.kernel.org/stable/c/ad27b4a51495490b815580d9b935e8eee14d1a9cPatch
- https://git.kernel.org/stable/c/aed709355fd05ef747e1af24a1d5d78cd7feb81ePatch
- https://git.kernel.org/stable/c/c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1ePatch
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.