System hang via unsynchronized camera mode change
Published Jul 8, 2025 · Updated Sep 2, 2026
Improper hardware synchronization in the Linux Exynos4 camera driver allows local users to corrupt image data or hang the system. The fimc_is_hw_change_mode() function configures a new camera mode and continues without waiting for the hardware-completion interrupt, so later operations can encounter unfinished hardware state. Low-privileged local access and an affected Exynos4 imaging device are required; the bounded consequences are corrupted camera data or a system hang.
Summary
What happened
Improper hardware synchronization in the Linux Exynos4 camera driver allows local users to corrupt image data or hang the system. The fimc_is_hw_change_mode() function configures a new camera mode and continues without waiting for the hardware-completion interrupt, so later operations can encounter unfinished hardware state. Low-privileged local access and an affected Exynos4 imaging device are required; the bounded consequences are corrupted camera data or a system hang.
The record
- CVE
- CVE-2025-38237
- Published
- Jul 8, 2025
- Updated
- Sep 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2026Record 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=3.10
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <14acbb5af101b7bb58c0952949bba4c5fdf0ee7e
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <2fbe83fe23f541798bcdd7d6b56a08d4ac205bad
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <71209954f1e8ff0f0ba944c8d3b64bbed83d400c
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <9b03c3ce32a685f9cb82d33c63fc18bfcee0ba1b
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <b0d92b94278561f43057003a73a17ce13b7c1a1a
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <bb97dfab7615fea97322b8a6131546e80f878a69
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <bd9f6ce7d512fa21249415c16af801a4ed5d97b6
- Affected versionversion=9a761e436843f228eaa2decda6d2c6dbd5ef1480 <e4077a10a25560ec0bd0b42322e4ea027d6f76e2
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