drm/hyperv: Fix address space leak when Hyper-V DRM device is removed
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.132, 6.12.20, 6.13.8, 6.6.84
- CVEs
- CVE-2025-21978
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 17:56 UTC · Revision 1
Source evidence
drm/hyperv: Fix address space leak when Hyper-V DRM device is removed
core-osv · Original sourcePublished 1 Apr 2025, 15:47 UTC
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.
osv:CVE-2025-21978
Kernel
Fixed versions: 6.1.132, 6.6.84, 6.12.20, 6.13.8
Complete source record
{
"id": "a09a41dd265834261672a8d4151706fa02dff764191a90927bbfc195fa81f496",
"url": "https://osv.dev/vulnerability/CVE-2025-21978",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "drm/hyperv: Fix address space leak when Hyper-V DRM device is removed",
"summary": "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.",
"evidence": "osv:CVE-2025-21978",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.132",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.84",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.20",
"evidence": "/affected/1/ranges"
},
{
"value": "6.13.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-21978",
"aliases": [
"CVE-2025-21978"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "a0ab5abced550ddeefddb06055ed60779a54eb79"
},
{
"fixed": "c40cd24bfb9bfbb315c118ca14ebe6cf52e2dd1e"
},
{
"fixed": "ad27b4a51495490b815580d9b935e8eee14d1a9c"
},
{
"fixed": "24f1bbfb2be77dad82489c1468bbb14312aab129"
},
{
"fixed": "158242b56bf465a73e1edeac0fe828a8acad4499"
},
{
"fixed": "aed709355fd05ef747e1af24a1d5d78cd7feb81e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21978.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.0.0"
},
{
"fixed": "6.1.132"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.84"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.20"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.13.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21978.json"
}
}
],
"modified": "2026-10-28T02:30:38.494477318Z",
"provider": "osv",
"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",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21978.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-21978",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21978.json"
}
},
"related_cves": [
{
"value": "CVE-2025-21978",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505536,
"published_at": "2025-04-01T15:47:08.168+00:00"
}