Skip to main content
VulnerabilityPublished Updated

CVE-2025-38597: Linux kernel · NULL Pointer Dereference

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-38597· Medium

Not known to be exploited · CVSS 5.5 Medium · fixed in f9f68bf1d0efeadb6c427c9dbb30f307a7def19b : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
Patch
Available – fixed in f9f68bf1d0efeadb6c427c9dbb30f307a7def19b, e1eef239399927b368f70a716044fb10085627c8, 93857359a07e425b643178ce3c6e60a9e4605cac +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 604be85547ce4d61b89292d2f9a78c721b778c16, < f9f68bf1d0efeadb6c427c9dbb30f307a7def19b
Fixed in
  • f9f68bf1d0efeadb6c427c9dbb30f307a7def19b
LinuxLinuxAffected
  • ≥ 604be85547ce4d61b89292d2f9a78c721b778c16, < e1eef239399927b368f70a716044fb10085627c8
Fixed in
  • e1eef239399927b368f70a716044fb10085627c8
LinuxLinuxAffected
  • ≥ 604be85547ce4d61b89292d2f9a78c721b778c16, < 93857359a07e425b643178ce3c6e60a9e4605cac
Fixed in
  • 93857359a07e425b643178ce3c6e60a9e4605cac
LinuxLinuxAffected
  • ≥ 604be85547ce4d61b89292d2f9a78c721b778c16, < 38682edbbad272b5f8c7bf55128b42cd10626f73
Fixed in
  • 38682edbbad272b5f8c7bf55128b42cd10626f73
LinuxLinuxAffected
  • ≥ 604be85547ce4d61b89292d2f9a78c721b778c16, < 45be183b9944f765b77623daffb024cb38d192bf
Fixed in
  • 45be183b9944f765b77623daffb024cb38d192bf
LinuxLinuxAffected
  • ≥ 604be85547ce4d61b89292d2f9a78c721b778c16, < 8fc974776c668fef1fc73fefbf573a076bb073e8
Fixed in
  • 8fc974776c668fef1fc73fefbf573a076bb073e8

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.

References

Community reviews

Loading reviews…