VYPR
Unrated severityNVD Advisory· Published Nov 12, 2025· Updated Apr 15, 2026

CVE-2025-40110

CVE-2025-40110

Description

In the Linux kernel, the following vulnerability has been resolved:

drm/vmwgfx: Fix a null-ptr access in the cursor snooper

Check that the resource which is converted to a surface exists before trying to use the cursor snooper on it.

vmw_cmd_res_check allows explicit invalid (SVGA3D_INVALID_ID) identifiers because some svga commands accept SVGA3D_INVALID_ID to mean "no surface", unfortunately functions that accept the actual surfaces as objects might (and in case of the cursor snooper, do not) be able to handle null objects. Make sure that we validate not only the identifier (via the vmw_cmd_res_check) but also check that the actual resource exists before trying to do something with it.

Fixes unchecked null-ptr reference in the snooping code.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A null-pointer dereference in the VMwgfx DRM driver's cursor snooper can be triggered by a malformed command, leading to a kernel crash.

Vulnerability

In the Linux kernel's VMwgfx DRM driver, the cursor snooper functionality performs an unchecked null-pointer dereference when processing a command that references an invalid surface resource. The function vmw_cmd_res_check accepts the identifier SVGA3D_INVALID_ID to represent "no surface" per the SVGA protocol [1]. However, the cursor snooping code does not handle a null resource object resulting from such an identifier, leading to a null-ptr access [2].

Exploitation

An attacker with access to the VMwgfx device interface (e.g., a local user with permissions to submit command buffers to the virtual GPU) can craft a command that includes an invalid surface handle. By passing an invalid resource identifier to the cursor snooper without additional validation, the kernel attempts to dereference a null pointer [3]. No authentication beyond local system access to the graphics device is required.

Impact

Successful exploitation causes a kernel oops or panic, resulting in a denial of service (DoS). The vulnerability does not appear to allow code execution beyond the immediate null-ptr dereference crash [4].

Mitigation

The fix adds a check to verify that the resource object exists after vmw_cmd_res_check before proceeding with cursor snooping [3][4]. Patches have been committed to the Linux kernel stable tree. Affected systems should update to a kernel version containing the commit that adds the null-resource check.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

7

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

7

News mentions

0

No linked articles in our index yet.