CVE-2025-21978
drm/hyperv: Fix address space leak when Hyper-V DRM device is removed
CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th
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.
| Vendor | linux |
| Product | linux |
| Ecosystems | |
| Industries | Technology |
| Published | Apr 1, 2025 |
| Last Updated | May 11, 2026 |
Stay Ahead of the Next One
Get instant alerts for linux linux
Be the first to know when new unknown vulnerabilities affecting linux linux are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
Linux / Linux
a0ab5abced550ddeefddb06055ed60779a54eb79 < c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e a0ab5abced550ddeefddb06055ed60779a54eb79 < ad27b4a51495490b815580d9b935e8eee14d1a9c a0ab5abced550ddeefddb06055ed60779a54eb79 < 24f1bbfb2be77dad82489c1468bbb14312aab129 a0ab5abced550ddeefddb06055ed60779a54eb79 < 158242b56bf465a73e1edeac0fe828a8acad4499 a0ab5abced550ddeefddb06055ed60779a54eb79 < aed709355fd05ef747e1af24a1d5d78cd7feb81e
Linux / Linux
6.0
References
git.kernel.org: https://git.kernel.org/stable/c/c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e git.kernel.org: https://git.kernel.org/stable/c/ad27b4a51495490b815580d9b935e8eee14d1a9c git.kernel.org: https://git.kernel.org/stable/c/24f1bbfb2be77dad82489c1468bbb14312aab129 git.kernel.org: https://git.kernel.org/stable/c/158242b56bf465a73e1edeac0fe828a8acad4499 git.kernel.org: https://git.kernel.org/stable/c/aed709355fd05ef747e1af24a1d5d78cd7feb81e lists.debian.org: https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html