LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52470: drm/radeon: check the alloc_workqueue return value in radeon_crtc_init()

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: check the alloc_workqueue return value in radeon_crtc_init() check the alloc_workqueue return value in radeon_crtc_init() to avoid null-ptr-deref.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-52470 is a Linux kernel reliability flaw in the Radeon graphics driver. If a workqueue allocation fails during display initialization, the kernel could hit a null pointer dereference. The cited sources show stable kernel fixes, but no CVSS score or active exploitation evidence.

Executive priority

Handle through normal kernel patch management unless Radeon-dependent systems are business-critical. There is no cited active exploitation, but kernel null dereferences can cause outages on affected systems.

Technical view

The flaw is in drm/radeon radeon_crtc_init(). The fix checks alloc_workqueue() before use to avoid null-pointer dereference. The CVE record lists affected Linux kernel versions/ranges and stable commit references across maintained branches. Impact details are limited in the provided sources.

Likely exposure

Exposure is most likely on Linux systems using the drm/radeon driver, especially hosts with older AMD Radeon graphics hardware or kernels in the listed affected ranges. Downstream distribution package status must be confirmed separately.

Exploitation context

The source bundle does not report KEV listing, public exploitation, exploit maturity, or remote attack details. Treat this as a potential local or device-triggered kernel stability issue unless vendor advisories provide stronger evidence.

Researcher notes

Evidence supports a missing allocation-failure check in radeon_crtc_init(), fixed by stable kernel commits. The bundle lacks CVSS, detailed attack prerequisites, and distribution-specific fixed package versions beyond Debian advisory references.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Debian LTS advisories if running affected Debian LTS kernels.
  • Prioritize systems with Radeon GPUs or the radeon driver loaded.
  • Track distribution security advisories for package-specific fixed versions.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Check whether the radeon kernel module is present or loaded.
  • Compare installed kernels with vendor security advisory fixed packages.
  • Confirm the stable fix commit is included in custom kernels.
Prepared
Confidence
medium
Sources
12

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-2023-52470 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
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337, fa7f517cb26eb1a1a1f0baffcced39f6c3ec3337unaffected
LinuxLinux3.16, 0, 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

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