LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38597: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port

In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: vop2: fail cleanly if missing a primary plane for a video-port Each window of a vop2 is usable by a specific set of video ports, so while binding the vop2, we look through the list of available windows trying to find one designated as primary-plane and usable by that specific port. The code later wants to use drm_crtc_init_with_planes with that found primary plane, but nothing has checked so far if a primary plane was actually found. For whatever reason, the rk3576 vp2 does not have a usable primary window (if vp0 is also in use) which brought the issue to light and ended in a null-pointer dereference further down. As we expect a primary-plane to exist for a video-port, add a check at the end of the window-iteration and fail probing if none was found.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects certain Rockchip display-controller configurations. If the driver cannot find a required primary display plane, it may dereference a null pointer instead of failing cleanly. The visible business impact is likely device instability during display initialization, not a broadly exploitable internet-facing flaw based on the provided sources.

Executive priority

Treat as a targeted reliability fix for Rockchip-based Linux devices rather than an enterprise-wide emergency. Prioritize embedded, appliance, kiosk, or product fleets using RK3576 or Rockchip VOP2 display paths. Monitor vendor kernel updates and patch during the next appropriate maintenance window unless instability is already observed.

Technical view

The Rockchip VOP2 DRM driver searched for a primary plane usable by each video port, then later used that pointer with drm_crtc_init_with_planes. On RK3576 VP2 in some configurations, no usable primary window may exist, causing a null-pointer dereference during probe. The fix adds a check and fails probing when no primary plane is found.

Likely exposure

Exposure appears limited to Linux systems using the Rockchip VOP2 DRM driver, especially RK3576 display configurations. General servers, desktops, and devices without this hardware or driver are unlikely to be affected. The affected version data is incomplete and should be verified against vendor kernel packages.

Exploitation context

The bundle reports KEV false and provides no evidence of active exploitation. The described failure occurs during driver binding/probing on specific hardware configuration. No remote attack path, privilege boundary crossing, or public exploit is described in the supplied sources.

Researcher notes

The sources do not provide CVSS, CWE, exploitability details, or complete affected-version boundaries. Analysis should stay close to the kernel commit message: missing primary-plane validation leads to null-pointer dereference during VOP2 probe. Confirm exposure through hardware, kernel configuration, and downstream backport status.

Mitigation direction

  • Apply vendor or distribution kernels containing the referenced upstream stable fixes.
  • Check Linux kernel vendor guidance for exact fixed package versions.
  • Prioritize affected Rockchip-based devices that use the VOP2 DRM driver.
  • Avoid deploying unpatched affected kernels to RK3576 display configurations.

Validation and detection

  • Inventory devices for Rockchip SoCs and VOP2 DRM driver usage.
  • Compare deployed kernel versions with vendor advisories and referenced fix commits.
  • Review boot and kernel logs for Rockchip DRM probe failures or null dereferences.
  • Test fixed kernels on representative RK3576 display configurations before rollout.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2025-38597 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux604be85547ce4d61b89292d2f9a78c721b778c16, 604be85547ce4d61b89292d2f9a78c721b778c16, 604be85547ce4d61b89292d2f9a78c721b778c16unaffected
LinuxLinux5.19, 0, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.