LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53542: ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy

In the Linux kernel, the following vulnerability has been resolved: ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy For some reason, the driver adding support for Exynos5420 MIPI phy back in 2016 wasn't used on Exynos5420, which caused a kernel panic. Add the proper compatible for it.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects ARM Exynos5420 systems where the device tree used the wrong MIPI video PHY compatibility data. The described impact is a kernel panic, so the business risk is service interruption on affected hardware rather than confirmed data compromise.

Executive priority

Handle through normal kernel maintenance unless Exynos5420 devices support critical services. There is no source evidence of active exploitation, but kernel panic risk can still affect availability for embedded or specialized systems.

Technical view

The fix changes Exynos device tree data to use the Exynos5420-compatible MIPI video PHY. The CVE description says prior support existed but was not applied to Exynos5420, causing a kernel panic. The bundle provides Linux affected version ranges and stable kernel commit references, but no CVSS, CWE, or exploit details.

Likely exposure

Exposure appears limited to Linux deployments running affected kernels on ARM Exynos5420 hardware using the MIPI video PHY path. Organizations without Exynos5420 systems are unlikely to be exposed based on the provided evidence.

Exploitation context

The source bundle does not show CISA KEV listing or any cited active exploitation. It describes a kernel panic condition, but provides no trigger details, attacker requirements, or evidence of remote exploitation.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or detailed affected product matrix beyond Linux kernel versions and commit references. Treat version exposure carefully because downstream vendors may backport the fix without changing major kernel versions.

Mitigation direction

  • Check vendor kernel advisories for CVE-2023-53542 applicability.
  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Prioritize affected business-critical Exynos5420 systems first.
  • Track distribution backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux systems using ARM Exynos5420 hardware.
  • Compare running kernel builds against vendor fixed versions or referenced commits.
  • Review boot and crash logs for MIPI video PHY related panics.
  • Confirm distribution advisories map CVE-2023-53542 to installed packages.
Prepared
Confidence
medium
Sources
10

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-53542 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
9Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105, d1ed0d21695f632f8ec7bf8588abcf6a8da2b105unaffected
LinuxLinux4.2, 0, 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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