Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39923dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees

Description

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/[email protected]/ [2]: https://lore.kernel.org/r/[email protected]/

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39923, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 95% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 2e257a6125c63350f00dc42b9674f20fd3cf4a9f
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4c
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 555bd16351a35c79efb029a196975a5a27f7fbc4
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < ebf6c7c908e5999531c3517289598f187776124f
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 1fc14731f0be4885e60702b9596d14d9a79cf053
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 0ff9df758af7022d749718fb6b8385cc5693acf3
    • affected 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 – < 5068b5254812433e841a40886e695633148d362d
    • affected cecf8a69042b3a54cb843223756c10ee8a8665e3
    • affected 909474cd384cb206f33461fbd18089cf170533f8
    • affected 5e0986f7caf17d7b1acd2092975360bf8e88a57d
    • affected 4.9.104 – < 4.10
    • affected 4.14.45 – < 4.15
    • affected 4.16.13 – < 4.17
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.4.300 – ≤ 5.4.*
    • unaffected 5.10.245 – ≤ 5.10.*
    • unaffected 5.15.194 – ≤ 5.15.*
    • unaffected 6.1.153 – ≤ 6.1.*
    • unaffected 6.6.107 – ≤ 6.6.*
    • unaffected 6.12.48 – ≤ 6.12.*
    • unaffected 6.16.8 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39923 badge
[![CVE-2025-39923](https://cveledger.app/badge/CVE-2025-39923.svg)](https://cveledger.app/cve/CVE-2025-39923)

Record last updated .