VYPR
Unrated severityNVD Advisory· Published Dec 16, 2025· Updated Apr 15, 2026

CVE-2025-68228

CVE-2025-68228

Description

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

drm/plane: Fix create_in_format_blob() return value

create_in_format_blob() is either supposed to return a valid pointer or an error, but never NULL. The caller will dereference the blob when it is not an error, and thus will oops if NULL returned. Return proper error values in the failure cases.

AI Insight

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

A NULL pointer dereference in Linux kernel's drm_plane.c create_in_format_blob() could cause a system crash (oops) when the function returns NULL instead of an error pointer.

Vulnerability

Overview

In the Linux kernel, the create_in_format_blob() function in drm/plane.c was found to return NULL in certain failure cases instead of a proper error pointer. The function is designed to return either a valid pointer or an error value (via ERR_PTR()), but some error paths returned NULL. This violates the contract with callers, which check for errors using IS_ERR() and dereference the returned pointer when it is not an error. If NULL is returned, the caller will dereference it, leading to a NULL pointer dereference and a kernel oops (crash) [1].

Exploitation and

Impact

The vulnerability is triggered when create_in_format_blob() encounters an allocation failure or other error condition. An attacker would need to be able to trigger such a failure, potentially by exhausting memory or other resources. The attack surface is local, requiring the ability to invoke DRM plane operations, typically through a graphics system call. No special privileges are mentioned, but the attacker must have access to the DRM subsystem. The impact is a denial of service (system crash) due to the NULL pointer dereference [1].

Mitigation

The fix was applied in the Linux kernel stable tree, changing the NULL returns to appropriate error codes using ERR_PTR(). Users should update to a kernel version containing the commit cead55e24cf9e092890cf51c0548eccd7569defa or later. No workaround is mentioned; the patch is the recommended mitigation [1].

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

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

2

News mentions

0

No linked articles in our index yet.