Skip to content
CVE PROGRAM SOURCE RECORDUnscored

CVE-2025-39923

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

Read JSON ↗CVE.org ↗
Status
Published
Published
Updated
Assigning organization
Linux

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/CY01EKQVWE36.B9X5TDXAREPF@fairphone.com/ [2]: https://lore.kernel.org/r/20230626145959.646747-1-krzysztof.kozlowski@linaro.org/

Affected products

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

Linux Linux

Default version status: unaffected

  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 2e257a6125c63350f00dc42b9674f20fd3cf4a9faffected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2affected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4caffected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 555bd16351a35c79efb029a196975a5a27f7fbc4affected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < ebf6c7c908e5999531c3517289598f187776124faffected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 1fc14731f0be4885e60702b9596d14d9a79cf053affected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 0ff9df758af7022d749718fb6b8385cc5693acf3affected
  • 48d163b1aa6e7f650c0b7a4f9c61c387a6def868 to < 5068b5254812433e841a40886e695633148d362daffected
  • cecf8a69042b3a54cb843223756c10ee8a8665e3affected
  • 909474cd384cb206f33461fbd18089cf170533f8affected
  • 5e0986f7caf17d7b1acd2092975360bf8e88a57daffected
  • 4.9.104 to < 4.10affected
  • 4.14.45 to < 4.15affected
  • 4.16.13 to < 4.17affected

Linux Linux

Default version status: affected

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

References