CVE-2025-39923

In the Linux kernel, the following vulnerability has been resolved: dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees When we don't have a clock specified in the device tree, we have no way to ensure the BAM is on. This is often the case for remotely-controlled or remotely-powered BAM instances. In this case, we need to read num-channels from the DT to have all the necessary information to complete probing. However, at the moment invalid device trees without clock and without num-channels still continue probing, because the error handling is missing return statements. The driver will then later try to read the number of channels from the registers. This is unsafe, because it relies on boot firmware and lucky timing to succeed. Unfortunately, the lack of proper error handling here has been abused for several Qualcomm SoCs upstream, causing early boot crashes in several situations [1, 2]. Avoid these early crashes by erroring out when any of the required DT properties are missing. Note that this will break some of the existing DTs upstream (mainly BAM instances related to the crypto engine). However, clearly these DTs have never been tested properly, since the error in the kernel log was just ignored. It's safer to disable the crypto engine for these broken DTBs. [1]: https://lore.kernel.org/r/CY01EKQVWE36.B9X5TDXAREPF@fairphone.com/ [2]: https://lore.kernel.org/r/20230626145959.646747-1-krzysztof.kozlowski@linaro.org/

• https://git.kernel.org/stable/c/0ff9df758af7022d749718fb6b8385cc5693acf3Patch
• https://git.kernel.org/stable/c/1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2Patch
• https://git.kernel.org/stable/c/1fc14731f0be4885e60702b9596d14d9a79cf053Patch
• https://git.kernel.org/stable/c/2e257a6125c63350f00dc42b9674f20fd3cf4a9fPatch
• https://git.kernel.org/stable/c/5068b5254812433e841a40886e695633148d362dPatch
• https://git.kernel.org/stable/c/555bd16351a35c79efb029a196975a5a27f7fbc4Patch
• https://git.kernel.org/stable/c/6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4cPatch
• https://git.kernel.org/stable/c/ebf6c7c908e5999531c3517289598f187776124fPatch
• https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory

Published

Oct 1, 2025

Last Modified

Jun 17, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-39918In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39919In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-3992A vulnerability has been found in TOTOLINK N150RT 3.4.0-B201…8.8
• CVE-2025-39920In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39921In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39922In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2025-39924In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39925In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39926In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39927In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2025-39928In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39929In the Linux kernel, the following vulnerability has been re…5.5