Early-boot crash via missing device-tree error returns
Published Oct 1, 2025 · Updated May 23, 2026
Improper error handling in the Linux bam_dma driver allows local users to cause an early-boot crash on affected Qualcomm systems. The probe path continues after required device-tree properties are absent, then reads BAM registers without assurance that the hardware is powered. Reachability requires a Qualcomm BAM instance whose device tree omits a clock and required channel data; the bounded consequence is an early-boot crash.
Summary
What happened
Improper error handling in the Linux bam_dma driver allows local users to cause an early-boot crash on affected Qualcomm systems. The probe path continues after required device-tree properties are absent, then reads BAM registers without assurance that the hardware is powered. Reachability requires a Qualcomm BAM instance whose device tree omits a clock and required channel data; the bounded consequence is an early-boot crash.
The record
- CVE
- CVE-2025-39923
- Published
- Oct 1, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=4.14.45 <4.15
- Affected versionversion=4.16.13 <4.17
- Affected versionversion=4.17
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <0ff9df758af7022d749718fb6b8385cc5693acf3
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <1fc14731f0be4885e60702b9596d14d9a79cf053
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <2e257a6125c63350f00dc42b9674f20fd3cf4a9f
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <5068b5254812433e841a40886e695633148d362d
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <555bd16351a35c79efb029a196975a5a27f7fbc4
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4c
- Affected versionversion=48d163b1aa6e7f650c0b7a4f9c61c387a6def868 <ebf6c7c908e5999531c3517289598f187776124f
- Affected versionversion=4.9.104 <4.10
- Affected versionversion=5e0986f7caf17d7b1acd2092975360bf8e88a57d
- Affected versionversion=909474cd384cb206f33461fbd18089cf170533f8
- Affected versionversion=cecf8a69042b3a54cb843223756c10ee8a8665e3
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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