LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53714: drm/stm: ltdc: fix late dereference check

In the Linux kernel, the following vulnerability has been resolved: drm/stm: ltdc: fix late dereference check In ltdc_crtc_set_crc_source(), struct drm_crtc was dereferenced in a container_of() before the pointer check. This could cause a kernel panic. Fix this smatch warning: drivers/gpu/drm/stm/ltdc.c:1124 ltdc_crtc_set_crc_source() warn: variable dereferenced before check 'crtc' (see line 1119)

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53714 is a Linux kernel bug in the STM LTDC DRM display driver. A null pointer check happened after the pointer was already used, which could crash the kernel. The public record does not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat this as a targeted stability risk, not a confirmed widespread breach risk. Patch affected Linux systems during normal kernel maintenance, escalating only where STM display controller support is used in production or safety-sensitive devices.

Technical view

In drivers/gpu/drm/stm/ltdc.c, ltdc_crtc_set_crc_source() dereferenced struct drm_crtc via container_of() before checking whether crtc was null. The kernel fix moves the check before dereference to avoid a possible kernel panic.

Likely exposure

Exposure appears limited to Linux kernels containing the affected drm/stm/ltdc.c code path, especially systems using the STM LTDC DRM driver. The bundle lists Linux versions 5.18, 6.1.47, 6.4.12, and 6.5 as affected, but version semantics are incomplete.

Exploitation context

The source bundle only supports a kernel panic impact from a dereference-before-check bug. It does not cite public exploit code, active exploitation, KEV listing, privilege requirements, or a remote attack path.

Researcher notes

The record lacks CVSS, CWE, exploitability details, and complete affected-version boundaries. The strongest evidence is the kernel commit message describing dereference before null check and a possible panic. Avoid assuming broader impact without vendor confirmation.

Mitigation direction

  • Apply vendor kernel updates that include the cited stable fixes.
  • Prioritize systems using the STM LTDC DRM driver.
  • Consult Linux distribution guidance for exact fixed package versions.
  • Track the CVE until vendor severity and affected-version details are clearer.

Validation and detection

  • Inventory deployed kernel versions against the listed affected versions.
  • Check whether the STM LTDC DRM driver is present or enabled.
  • Confirm kernel packages include one of the cited stable commits.
  • Review crash telemetry for panics involving ltdc_crtc_set_crc_source().
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-2023-53714 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
LinuxLinux79b44684a14e363d24c299b772f037344ad8c8dc, 79b44684a14e363d24c299b772f037344ad8c8dc, 79b44684a14e363d24c299b772f037344ad8c8dcunaffected
LinuxLinux5.18, 0, 6.1.47, 6.4.12, 6.5affected
Weakness

CWE details

No CWE listed

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