CVE-2025-21978
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-401
- Record status
- Modified
Affected
- Linux Kernel < 6.1.132
- Linux Kernel < 6.6.84
- Linux Kernel < 6.12.20
- Linux Kernel < 6.13.8
- Linux Kernel 6.14
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-21978.md and follow it. Check whether this project is affected by CVE-2025-21978. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/158242b56bf465a73e1edeac0fe828a8acad4499
- https://git.kernel.org/stable/c/24f1bbfb2be77dad82489c1468bbb14312aab129
- https://git.kernel.org/stable/c/ad27b4a51495490b815580d9b935e8eee14d1a9c
- https://git.kernel.org/stable/c/aed709355fd05ef747e1af24a1d5d78cd7feb81e
- https://git.kernel.org/stable/c/c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e
References
- https://git.kernel.org/stable/c/158242b56bf465a73e1edeac0fe828a8acad4499
- https://git.kernel.org/stable/c/24f1bbfb2be77dad82489c1468bbb14312aab129
- https://git.kernel.org/stable/c/ad27b4a51495490b815580d9b935e8eee14d1a9c
- https://git.kernel.org/stable/c/aed709355fd05ef747e1af24a1d5d78cd7feb81e
- https://git.kernel.org/stable/c/c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html