Heimdall Security Logo

CVE-2025-39923

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.1%
Linux•Linux•Versions : 5.4.300, <=6.1.*, 6.16.8, <=6.12.*, <=6.16.*, 4.14.45, 6.17, 0, 4.9.104, <4.10, <ebf6c7c908e5999531c3517289598f187776124f, <1fc14731f0be4885e60702b9596d14d9a79cf053, 48d163b1aa6e7f650c0b7a4f9c61c387a6def868, <4.17, <=5.10.*, 5.15.194, <=6.6.*, cecf8a69042b3a54cb843223756c10ee8a8665e3, <1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2, 4.16.13, 6.6.107, 909474cd384cb206f33461fbd18089cf170533f8, 4.17, <=5.4.*, 6.1.153, <0ff9df758af7022d749718fb6b8385cc5693acf3, <6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4c, 5.10.245, 5e0986f7caf17d7b1acd2092975360bf8e88a57d, 6.12.48, <=*, <=5.15.*, <2e257a6125c63350f00dc42b9674f20fd3cf4a9f, <4.15, <5068b5254812433e841a40886e695633148d362d, <555bd16351a35c79efb029a196975a5a27f7fbc4

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/

Gravité et risque d'exploitation

CVE-2025-39923 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.15 %, ce qui la place devant 3.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 5.4.300, <=6.1.*, 6.16.8, <=6.12.*, <=6.16.*, 4.14.45, 6.17, 0, 4.9.104, <4.10, <ebf6c7c908e5999531c3517289598f187776124f, <1fc14731f0be4885e60702b9596d14d9a79cf053, 48d163b1aa6e7f650c0b7a4f9c61c387a6def868, <4.17, <=5.10.*, 5.15.194, <=6.6.*, cecf8a69042b3a54cb843223756c10ee8a8665e3, <1d98ba204d8a6db0d986c7f1aefaa0dcd1c007a2, 4.16.13, 6.6.107, 909474cd384cb206f33461fbd18089cf170533f8, 4.17, <=5.4.*, 6.1.153, <0ff9df758af7022d749718fb6b8385cc5693acf3, <6ac1599d0e78036d9d08efc2f58c2d91f0a3ee4c, 5.10.245, 5e0986f7caf17d7b1acd2092975360bf8e88a57d, 6.12.48, <=*, <=5.15.*, <2e257a6125c63350f00dc42b9674f20fd3cf4a9f, <4.15, <5068b5254812433e841a40886e695633148d362d, <555bd16351a35c79efb029a196975a5a27f7fbc4) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE