https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 09 May 2026 23:40:40 +0000 https://vulnerability.circl.lu/sighting/a19d1137-13c4-4553-95af-97fafc5d1353/export {"uuid": "a19d1137-13c4-4553-95af-97fafc5d1353", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21978", "type": "seen", "source": "https://t.me/cvedetector/21790", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-21978 - Hyper-V DRM Address Space Leak\", \n \"Content\": \"CVE ID : CVE-2025-21978 \nPublished : April 1, 2025, 4:15 p.m. | 1\u00a0hour, 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/hyperv: Fix address space leak when Hyper-V DRM device is removed \n \nWhen a Hyper-V DRM device is probed, the driver allocates MMIO space for \nthe vram, and maps it cacheable. If the device removed, or in the error \npath for device probing, the MMIO space is released but no unmap is done. \nConsequently the kernel address space for the mapping is leaked. \n \nFix this by adding iounmap() calls in the device removal path, and in the \nerror path during device probing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"01 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-01T19:44:38.000000Z"} {"uuid": "a19d1137-13c4-4553-95af-97fafc5d1353", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21978", "type": "seen", "source": "https://t.me/cvedetector/21790", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-21978 - Hyper-V DRM Address Space Leak\", \n \"Content\": \"CVE ID : CVE-2025-21978 \nPublished : April 1, 2025, 4:15 p.m. | 1\u00a0hour, 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/hyperv: Fix address space leak when Hyper-V DRM device is removed \n \nWhen a Hyper-V DRM device is probed, the driver allocates MMIO space for \nthe vram, and maps it cacheable. If the device removed, or in the error \npath for device probing, the MMIO space is released but no unmap is done. \nConsequently the kernel address space for the mapping is leaked. \n \nFix this by adding iounmap() calls in the device removal path, and in the \nerror path during device probing. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"01 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-01T19:44:38.000000Z"} https://vulnerability.circl.lu/sighting/a19d1137-13c4-4553-95af-97fafc5d1353/export Tue, 01 Apr 2025 19:44:38 +0000