Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0ff9df758af7022d749718fb6b8385cc5693acf3, 1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2, 1fc14731f0be4885e60702b9596d14d9a79cf053; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.

Low priority for now. Upgrade to Linux Linux 0ff9df758af7022d749718fb6b8385cc5693acf3, 1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2, 1fc14731f0be4885e60702b9596d14d9a79cf053; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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/

Published
Oct 1, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-39923

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • cecf8a69042b3a54cb843223756c10ee8a8665e3, 909474cd384cb206f33461fbd18089cf170533f8, 5e0986f7caf17d7b1acd2092975360bf8e88a57d, 4.17affected
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 2e257a6125c63350f00dc42b9674f20fd3cf4a9faffected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2affected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4caffected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 555bd16351a35c79efb029a196975a5a27f7fbc4affected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before ebf6c7c908e5999531c3517289598f187776124faffected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 1fc14731f0be4885e60702b9596d14d9a79cf053affected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 0ff9df758af7022d749718fb6b8385cc5693acf3affected · git
    • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 and later · before 5068b5254812433e841a40886e695633148d362daffected · git
    • 4.9.104 and later · before 4.10affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linuxbefore 5.10.247-15.10.247-1
Debian:12linuxbefore 6.1.153-16.1.153-1
Debian:13linuxbefore 6.12.48-16.12.48-1
Debian:14linuxbefore 6.16.8-16.16.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-39922Oct 1, 2025 · ixgbe: fix incorrect map used in eee linkmode
    28Monitor
  • ← EarlierCVE-2022-50436Oct 1, 2025 · ext4: don't set up encryption key during jbd2 transaction
    22Monitor
  • Later →CVE-2022-50437Oct 1, 2025 · drm/msm/hdmi: fix memory corruption with too many bridges
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0ff9df758af7022d749718fb6b8385cc5693acf3Vendor (CNA)
Linux Linux1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2Vendor (CNA)
Linux Linux1fc14731f0be4885e60702b9596d14d9a79cf053Vendor (CNA)
Linux Linux2e257a6125c63350f00dc42b9674f20fd3cf4a9fVendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.17Vendor (CNA)
Linux Linux5068b5254812433e841a40886e695633148d362dVendor (CNA)
Linux Linux555bd16351a35c79efb029a196975a5a27f7fbc4Vendor (CNA)
Linux Linux6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4cVendor (CNA)
Linux Linuxebf6c7c908e5999531c3517289598f187776124fVendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.05.15.200.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records