CVE-2025-22097: drm/vkms: Fix use after free and double free on init error
Published Apr 16, 2025
·Updated
drm/vkms: Fix use after free and double free on init error
Affected Software
15 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.12<5.15.180
Linux Linux kernel>=5.16<6.1.134
Linux Linux kernel>=6.2<6.6.87
Linux Linux kernel>=6.7<6.12.23
Linux Linux kernel>=6.13<6.13.11
Linux Linux kernel>=6.14<6.14.2
Microsoft cbl2 kernel 5.15.176.3-3
Microsoft cbl2 kernel 5.15.176.3-3
Microsoft azl3 kernel 6.6.85.1-4
Microsoft cbl2 kernel 5.15.180.1-1
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1
Event History
Apr 16, 2025
CVE Published
via MITRE·02:12 PM
Data Sourced
via MITRE·02:12 PM
Description
Data Sourced
via Red Hat·03:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 5, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-22097?
The severity of CVE-2025-22097 is classified as moderate due to its nature of allowing potential memory corruption.
2
How do I fix CVE-2025-22097?
To fix CVE-2025-22097, upgrade to the latest stable version of the Linux kernel that includes the patched code.
3
What systems are affected by CVE-2025-22097?
CVE-2025-22097 affects various versions of the Linux kernel that implement the drm/vkms driver.
4
What are the risks associated with CVE-2025-22097?
The risks associated with CVE-2025-22097 include potential system instability and exploitation that could lead to unauthorized access or denial of service.
5
Is there a workaround for CVE-2025-22097?
Currently, there are no publicly recommended workarounds for CVE-2025-22097 other than updating to the patched kernel.