Kernel panic via incorrect MIPI PHY binding
Published Oct 4, 2025 · Updated Oct 4, 2025
Kernel panic in Linux 4.2 through 6.2.2 allows local users to crash Exynos5420 systems by exercising the MIPI video PHY. The exynos5420.dtsi device tree labels the MIPI video PHY with the generic samsung,s5pv210-mipi-video-phy compatible, so the kernel selects a driver path that lacks Exynos5420 handling. Exploitation requires local low-privileged access to an Exynos5420 system and interrupts the host by panicking its kernel.
Summary
What happened
Kernel panic in Linux 4.2 through 6.2.2 allows local users to crash Exynos5420 systems by exercising the MIPI video PHY. The exynos5420.dtsi device tree labels the MIPI video PHY with the generic samsung,s5pv210-mipi-video-phy compatible, so the kernel selects a driver path that lacks Exynos5420 handling. Exploitation requires local low-privileged access to an Exynos5420 system and interrupts the host by panicking its kernel.
The record
- CVE
- CVE-2023-53542
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <199624f3144d79fab1cff533ce6a4b82390520a3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29961ee63dd676cc67f7c00f76faa21e11f0d7c6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2e68a0f7bc576318a58335c31c542b358bc63f83
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <537bdfc1a67836fbd68bbe4210bc380f72cca47f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5d5aa219a790d61cad2c38e1aa32058f16ad2f0b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c075aa3467a799855a92289a3c619afc0a2ad193
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f10001af0f7246cf3e43530d25f8d59a8db10df6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f2a6198f5ed7d6e4e06d87a4de007f2e45cc9583
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo