CVE-2023-53542

ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy

MEDIUM

5.5

CVSS Score

Published: October 4, 2025 at 03:16 PM UTC

Updated: June 17, 2026 at 06:45 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.15 ≤ v < 4.19.2764.2 ≤ v < 4.14.3084.2 ≤ v < 4.19.2764.2 ≤ v < 5.10.1734.2 ≤ v < 5.15.994.2 ≤ v < 5.4.2354.2 ≤ v < 6.1.164.2 ≤ v < 6.2.34.2 ≤ v < 6.34.20 ≤ v < 5.4.2355.11 ≤ v < 5.15.995.16 ≤ v < 6.1.165.5 ≤ v < 5.10.1736.2 ≤ v < 6.2.34.2d1ed0d21695f632f8ec7bf8588abcf6a8da2b105

Vendor states this is fixed in 199624f3144d79fab1cff533ce6a4b82390520a3 (fixed)

Vendor states this is fixed in 29961ee63dd676cc67f7c00f76faa21e11f0d7c6 (fixed)

Vendor states this is fixed in 2e68a0f7bc576318a58335c31c542b358bc63f83 (fixed)

Vendor states this is fixed in 537bdfc1a67836fbd68bbe4210bc380f72cca47f (fixed)

Vendor states this is fixed in 5d5aa219a790d61cad2c38e1aa32058f16ad2f0b (fixed)

Vendor states this is fixed in c075aa3467a799855a92289a3c619afc0a2ad193 (fixed)

Vendor states this is fixed in f10001af0f7246cf3e43530d25f8d59a8db10df6 (fixed)

Vendor states this is fixed in f2a6198f5ed7d6e4e06d87a4de007f2e45cc9583 (fixed)

Vendor states this is fixed in 4.14.308 (unaffected)

Vendor states this is fixed in 4.19.276 (unaffected)

Vendor states this is fixed in 4.2 (unaffected)

Vendor states this is fixed in 5.10.173 (unaffected)