CVE-2022-48887: drm/vmwgfx: Remove rcu locks from user resources
In the Linux kernel, the following vulnerability has been resolved:
drm/vmwgfx: Remove rcu locks from user resources
User resource lookups used rcu to avoid two extra atomics. Unfortunately
the rcu paths were buggy and it was easy to make the driver crash by
submitting command buffers from two different threads. Because the
lookups never show up in performance profiles replace them with a
regular spin lock which fixes the races in accesses to those shared
resources.
Fixes kernel oops'es in IGT's vmwgfx execution_buffer stress test and
seen crashes with apps using shared resources.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash systems using the vmwgfx graphics driver when shared graphics resources are accessed concurrently. The source describes kernel oopses during stress testing and crashes in applications using shared resources. Public data does not provide CVSS, CWE, confirmed exploitation, or a broader impact claim.
Executive priority
Treat this as an availability risk for affected Linux virtual graphics environments. Prioritize normal kernel patching, with faster action where vmwgfx crashes would affect production reliability. There is no source-backed evidence of active exploitation.
Technical view
The vmwgfx DRM driver used RCU-protected user resource lookups. The RCU paths were race-prone when command buffers were submitted from two threads, causing crashes. The upstream resolution replaces those lookups with a regular spin lock because the optimization was not performance-critical.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds with the drm/vmwgfx driver in use. The bundle lists Linux kernel affected version markers including 4.20, 6.1.7, and 6.2, but downstream package mapping is not provided.
Exploitation context
The sources mention reproducible crashes in IGT's vmwgfx execution_buffer stress test and crashes from applications using shared resources. There is no KEV listing and no cited evidence of active exploitation in the provided bundle.
Researcher notes
The vulnerability is a concurrency race in vmwgfx user resource lookup paths. The source only supports crash/oops impact, not privilege escalation or data exposure. Affected-version precision depends on downstream kernel backports, so validate against vendor kernel metadata.
Mitigation direction
Apply kernel updates containing the referenced stable fixes.
Check Linux distribution advisories for exact package versions and backports.
Prioritize systems where vmwgfx is loaded or virtual graphics is used.
If patch timing is unclear, seek vendor guidance for supported mitigations.
Validation and detection
Inventory kernel versions and whether drm/vmwgfx is loaded.
Map installed kernel packages to distribution advisories or fixed commits.
Review crash logs for vmwgfx-related kernel oops entries.
Confirm updated kernels include the referenced stable commits.
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.
cve · low confidence lookup
CVE-2022-48887 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.