| From bippy-7c5fe7eed585 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-21978: drm/hyperv: Fix address space leak when Hyper-V DRM device is removed |
| |
| 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. |
| |
| The Linux kernel CVE team has assigned CVE-2025-21978 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.0 with commit a0ab5abced550ddeefddb06055ed60779a54eb79 and fixed in 6.1.132 with commit c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e |
| Issue introduced in 6.0 with commit a0ab5abced550ddeefddb06055ed60779a54eb79 and fixed in 6.6.84 with commit ad27b4a51495490b815580d9b935e8eee14d1a9c |
| Issue introduced in 6.0 with commit a0ab5abced550ddeefddb06055ed60779a54eb79 and fixed in 6.12.20 with commit 24f1bbfb2be77dad82489c1468bbb14312aab129 |
| Issue introduced in 6.0 with commit a0ab5abced550ddeefddb06055ed60779a54eb79 and fixed in 6.13.8 with commit 158242b56bf465a73e1edeac0fe828a8acad4499 |
| Issue introduced in 6.0 with commit a0ab5abced550ddeefddb06055ed60779a54eb79 and fixed in 6.14 with commit aed709355fd05ef747e1af24a1d5d78cd7feb81e |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-21978 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/gpu/drm/hyperv/hyperv_drm_drv.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e |
| https://git.kernel.org/stable/c/ad27b4a51495490b815580d9b935e8eee14d1a9c |
| https://git.kernel.org/stable/c/24f1bbfb2be77dad82489c1468bbb14312aab129 |
| https://git.kernel.org/stable/c/158242b56bf465a73e1edeac0fe828a8acad4499 |
| https://git.kernel.org/stable/c/aed709355fd05ef747e1af24a1d5d78cd7feb81e |
