Linux Kernel up to 6.1.152/6.6.106/6.12.47/6.16.7 dmaengine bam_dma state issue

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.1.152/6.6.106/6.12.47/6.16.7 and classified as critical. The affected element is the function bam_dma of the component dmaengine. This manipulation causes state issue. This vulnerability is tracked as CVE-2025-39923. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.1.152/6.6.106/6.12.47/6.16.7 and classified as critical. Affected by this vulnerability is the function bam_dma of the component dmaengine. The manipulation with an unknown input leads to a state issue vulnerability. The CWE definition for the vulnerability is CWE-371. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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]/

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2025-39923 since 04/16/2025. The exploitation appears to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/20/2026).

The vulnerability scanner Nessus provides a plugin with the ID 269655 (Linux Distros Unpatched Vulnerability : CVE-2025-39923), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.153, 6.6.107, 6.12.48 or 6.16.8 eliminates this vulnerability. Applying the patch 555bd16351a35c79efb029a196975a5a27f7fbc4/ebf6c7c908e5999531c3517289598f187776124f/1fc14731f0be4885e60702b9596d14d9a79cf053/0ff9df758af7022d749718fb6b8385cc5693acf3/5068b5254812433e841a40886e695633148d362d is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (269655), EUVD (EUVD-2025-31828) and CERT Bund (WID-SEC-2025-2170). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel
  • Dell Secure Connect Gateway

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: State issue
CWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 269655
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-39923

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.153/6.6.107/6.12.48/6.16.8
Patch: 555bd16351a35c79efb029a196975a5a27f7fbc4/ebf6c7c908e5999531c3517289598f187776124f/1fc14731f0be4885e60702b9596d14d9a79cf053/0ff9df758af7022d749718fb6b8385cc5693acf3/5068b5254812433e841a40886e695633148d362d

Timelineinfo

04/16/2025 CVE reserved
10/01/2025 +168 days Advisory disclosed
10/01/2025 +0 days VulDB entry created
01/20/2026 +111 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-39923 (🔒)
GCVE (CVE): GCVE-0-2025-39923
GCVE (VulDB): GCVE-100-326497
EUVD: 🔒
CERT Bund: WID-SEC-2025-2170 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 10/01/2025 10:26
Updated: 01/20/2026 17:56
Changes: 10/01/2025 10:26 (59), 10/01/2025 13:35 (1), 10/02/2025 01:42 (7), 10/11/2025 08:48 (2), 11/25/2025 06:18 (1), 12/01/2025 18:54 (1), 01/08/2026 19:33 (1), 01/20/2026 17:56 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!