CVE-2023-52738Network attack vector

Kernel crash via mismatched scheduler cleanup

Published May 21, 2024 · Updated May 23, 2026

NULL pointer dereference in the Linux kernel AMD GPU fence driver allows attackers to crash the kernel during failed device cleanup. When an AMD GPU ring's scheduler initialization fails, amdgpu_fence_driver_sw_fini() calls drm_sched_fini() without a successful drm_sched_init(), dereferencing uninitialized scheduler state. The crash requires an AMD GPU and a driver probe failure before fence cleanup; public records identify no attacker-controlled way to cause that prerequisite.

CVSS severity5.3
Medium
EPSS probability0.80%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

NULL pointer dereference in the Linux kernel AMD GPU fence driver allows attackers to crash the kernel during failed device cleanup. When an AMD GPU ring's scheduler initialization fails, amdgpu_fence_driver_sw_fini() calls drm_sched_fini() without a successful drm_sched_init(), dereferencing uninitialized scheduler state. The crash requires an AMD GPU and a driver probe failure before fence cleanup; public records identify no attacker-controlled way to cause that prerequisite.

The record

CVE
CVE-2023-52738
Published
May 21, 2024
Updated
May 23, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-476, T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 21, 2024CVE publishedPublication date reported by the CVE source.
  2. May 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=067f44c8b4590c3f24d21a037578a478590f2175 <2bcbbef9cace772f5b7128b11401c515982de34b
  2. Affected versionversion=067f44c8b4590c3f24d21a037578a478590f2175 <2e557c8ca2c585bdef591b8503ba83b85f5d0afd
  3. Affected versionversion=067f44c8b4590c3f24d21a037578a478590f2175 <5ad7bbf3dba5c4a684338df1f285080f2588b535
  4. Affected versionversion=5.14.10 <5.15
  5. Affected versionversion=5.15
  6. Affected versionversion=8ba968ae672b3075794c8086aa164595b0175abe

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=067f44c8b4590c3f24d21a037578a478590f2175 <2bcbbef9cace772f5b7128b11401c515982de34b; version=067f44c8b4590c3f24d21a037578a478590f2175 <2e557c8ca2c585bdef591b8503ba83b85f5d0afd; version=067f44c8b4590c3f24d21a037578a478590f2175 <5ad7bbf3dba5c4a684338df1f285080f2588b535; version=5.14.10 <5.15; version=5.15; version=8ba968ae672b3075794c8086aa164595b0175abe

Published CVSS scores

5.3CISACVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
5.3UbuntuCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-476NULL Pointer Dereference
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo