CVE-2025-38027

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <=6.14.*, <6ba30f7aa2c550b2ac04f16b81a19a8c045b8660, 0, <5.17, <=6.6.*, <5578ab04bd7732f470fc614bbc0a924900399fb8, <d2a9a92bb4cc7568cff68241b0051dc7268bdc68, 6.1.140, bfff546aae50ae68ed395bf0e0848188d27b0ba3, 6.14.8, 6.15, <7bddac8603d4e396872c2fbf4403ec08e7b1d7c8, 6.6.92, <6b0cd72757c69bc2d45da42b41023e288d02e772, <=*, 6.12.30, 5.17

Description

In the Linux kernel, the following vulnerability has been resolved: regulator: max20086: fix invalid memory access max20086_parse_regulators_dt() calls of_regulator_match() using an array of struct of_regulator_match allocated on the stack for the matches argument. of_regulator_match() calls devm_of_regulator_put_matches(), which calls devres_alloc() to allocate a struct devm_of_regulator_matches which will be de-allocated using devm_of_regulator_put_matches(). struct devm_of_regulator_matches is populated with the stack allocated matches array. If the device fails to probe, devm_of_regulator_put_matches() will be called and will try to call of_node_put() on that stack pointer, generating the following dmesg entries: max20086 6-0028: Failed to read DEVICE_ID reg: -121 kobject: '\xc0$\xa5\x03' (000000002cebcb7a): is not initialized, yet kobject_put() is being called. Followed by a stack trace matching the call flow described above. Switch to allocating the matches array using devm_kcalloc() to avoid accessing the stack pointer long after it's out of scope. This also has the advantage of allowing multiple max20086 to probe without overriding the data stored inside the global of_regulator_match.

Gravité et risque d'exploitation

CVE-2025-38027 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.20 %, ce qui la place devant 8.8 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <=6.14.*, <6ba30f7aa2c550b2ac04f16b81a19a8c045b8660, 0, <5.17, <=6.6.*, <5578ab04bd7732f470fc614bbc0a924900399fb8, <d2a9a92bb4cc7568cff68241b0051dc7268bdc68, 6.1.140, bfff546aae50ae68ed395bf0e0848188d27b0ba3, 6.14.8, 6.15, <7bddac8603d4e396872c2fbf4403ec08e7b1d7c8, 6.6.92, <6b0cd72757c69bc2d45da42b41023e288d02e772, <=*, 6.12.30, 5.17) 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