LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52695: drm/amd/display: Check writeback connectors in create_validate_stream_for_sink

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check writeback connectors in create_validate_stream_for_sink [WHY & HOW] This is to check connector type to avoid unhandled null pointer for writeback connectors.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash affected systems when the AMD display driver handles writeback connectors without a required connector-type check. The public record describes a null pointer problem, not data theft or privilege escalation. Business impact is most likely availability risk on affected Linux systems using AMD display components.

Executive priority

Treat as a targeted availability issue unless vendor advisories add stronger severity evidence. Patch during normal kernel maintenance, with higher priority for Linux workstations, kiosks, or GPU-enabled systems where display reliability matters.

Technical view

CVE-2023-52695 is in drm/amd/display create_validate_stream_for_sink. The fix adds connector-type handling for writeback connectors to avoid an unhandled null pointer. The source bundle identifies Linux kernel 6.7 through 6.7.2 as affected, with resolution in stable kernel commits. No CVSS, CWE, or detailed exploit prerequisites are provided.

Likely exposure

Exposure appears limited to Linux systems running affected 6.7-series kernels with AMD display driver paths involving writeback connectors. Systems on unaffected kernels, non-Linux systems, or environments without the relevant AMD display stack are less likely exposed, based on the available sources.

Exploitation context

The provided sources do not report active exploitation, public exploit code, or CISA KEV listing. They describe a resolved kernel null pointer issue. Practical exploitability, local versus remote reachability, and required privileges are not established in the source bundle.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed trigger conditions are provided. Analysis should stay close to the kernel fix: connector-type validation prevents a null pointer when writeback connectors reach create_validate_stream_for_sink.

Mitigation direction

  • Update to a kernel or vendor package containing the referenced stable fixes.
  • Prioritize affected Linux systems using AMD display hardware or writeback connector functionality.
  • Check distribution advisories for backported fixes in vendor-maintained kernels.
  • Monitor the CVE record and kernel stable branches for updated severity details.

Validation and detection

  • Inventory Linux kernel versions and identify systems in the affected 6.7-series range.
  • Confirm whether AMD display driver components are present and active.
  • Verify the running kernel includes the referenced stable fix commits or vendor backport.
  • Review crash reports for null pointer failures in drm/amd/display paths.
Prepared
Confidence
medium
Sources
4

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-52695 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
3Source 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
LinuxLinux60e034f28600399705d79d4629dddcc301076e54, 60e034f28600399705d79d4629dddcc301076e54unaffected
LinuxLinux6.7, 0, 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.