CVE-2025-22097: drm/vkms: Fix use after free and double free on init error
In the Linux kernel, the following vulnerability has been resolved:
drm/vkms: Fix use after free and double free on init error
If the driver initialization fails, the vkms_exit() function might
access an uninitialized or freed default_config pointer and it might
double free it.
Fix both possible errors by initializing default_config only when the
driver initialization succeeded.
Security readout for executives and security teams
Plain-English summary
CVE-2025-22097 is a Linux kernel memory-safety flaw in the vkms graphics driver error path. If driver initialization fails, the cleanup code may use or free invalid memory. The CVSS score is high, but the published vector indicates local, low-privilege access is required; there is no cited evidence of active exploitation.
Executive priority
Treat as a high-priority kernel maintenance item, especially for shared Linux infrastructure. It is not currently supported by cited evidence of active exploitation, but kernel memory corruption can have serious confidentiality, integrity, and availability impact if reachable locally.
Technical view
The issue is a CWE-416 use-after-free/double-free in drm/vkms. vkms_exit() may access an uninitialized or freed default_config pointer after initialization failure. Kernel stable commits fix this by initializing default_config only after successful driver initialization. CVSS 3.1 is 7.8: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Systems running affected Linux kernel versions with the vkms DRM driver code present are the relevant exposure. Risk is most important on multi-user Linux hosts, developer systems, CI runners, and desktops where local users or workloads may interact with kernel graphics components.
Exploitation context
The provided sources do not show public exploitation or CISA KEV listing. The CVSS vector indicates exploitation is local, requires low privileges, and needs no user interaction. The vulnerable condition is tied to a vkms driver initialization failure path, not a remote network service.
Researcher notes
Evidence is limited to the CVE record, Linux stable commits, and a Debian LTS advisory. The affected version data in the bundle mixes commit identifiers and kernel release numbers, so validate against distribution backports rather than upstream version numbers alone.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
For Debian LTS systems, review the linked Debian advisory and update accordingly.
If immediate patching is not possible, check vendor guidance for safe interim mitigations.
Prioritize shared or multi-user Linux systems before single-user controlled hosts.
Validation and detection
Inventory Linux kernel versions across servers, desktops, containers hosts, and CI runners.
Check whether installed kernels include the referenced stable commits or vendor backports.
Confirm Debian LTS hosts have applied the relevant linux package advisory updates.
Review kernel configuration and module inventory for vkms exposure where operationally relevant.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.