Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38597, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 604be85547ce4d61b89292d2f9a78c721b778c16 – < 93857359a07e425b643178ce3c6e60a9e4605cac
    • affected 604be85547ce4d61b89292d2f9a78c721b778c16 – < 45be183b9944f765b77623daffb024cb38d192bf
    • affected 604be85547ce4d61b89292d2f9a78c721b778c16 – < 8fc974776c668fef1fc73fefbf573a076bb073e8
    • affected 604be85547ce4d61b89292d2f9a78c721b778c16 – < e1eef239399927b368f70a716044fb10085627c8
    • affected 604be85547ce4d61b89292d2f9a78c721b778c16 – < 38682edbbad272b5f8c7bf55128b42cd10626f73
    • affected 604be85547ce4d61b89292d2f9a78c721b778c16 – < f9f68bf1d0efeadb6c427c9dbb30f307a7def19b
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38597 badge
[![CVE-2025-38597](https://cveledger.app/badge/CVE-2025-38597.svg)](https://cveledger.app/cve/CVE-2025-38597)

Record last updated .