CVE-2026-90296

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, <=6.1.*, <=6.12.*, 5.15.221, <0f77d1a0a25056146eea1f8619fa06ce287c91f7, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, 0, 5.10.270, 6.1.188, 6.18.52, <=5.10.*, <=6.6.*, 6.6.157, <22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, 7.2.6, <=6.18.*, <493c4d5982f037f288509a1cee352b8b9705fb38, 6.12.110, 3.14, <=7.2.*, <d91f07381e2b70578ff92b83d9422ac31e7b9096, <9e314b3ecd2594958d4f4999313641290ad28ebe, <3.14, <=*, <92e53a5274276a7b1ca815b9aacebea4fb7efe75, <=5.15.*, <e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: cpufreq: imx6q: fix devres accumulation across driver rebind imx6_soc_volt is allocated with devm_kcalloc(cpu_dev, ...), where cpu_dev is the CPU device from get_cpu_device(0). That device is never unbound, so its devres list is never released, and imx6q_cpufreq_remove() does not free the array either. Every probe therefore adds an allocation that stays for the lifetime of the system. Allocate against the platform device instead. Its devres is released when the driver is unbound, which is exactly the lifetime the array wants: imx6q_set_target() reads it, and nothing may reach that after cpufreq_unregister_driver(). That makes the array actually go away on unbind, so also clear the file-scope pointer in remove and on the failed-probe path, rather than leave it pointing at memory devres is about to release. Tested by rebinding the driver on qemu's mcimx6ul-evk.

Gravité et risque d'exploitation

CVE-2026-90296 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.22 %, ce qui la place devant 11.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, <=6.1.*, <=6.12.*, 5.15.221, <0f77d1a0a25056146eea1f8619fa06ce287c91f7, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, 0, 5.10.270, 6.1.188, 6.18.52, <=5.10.*, <=6.6.*, 6.6.157, <22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, 7.2.6, <=6.18.*, <493c4d5982f037f288509a1cee352b8b9705fb38, 6.12.110, 3.14, <=7.2.*, <d91f07381e2b70578ff92b83d9422ac31e7b9096, <9e314b3ecd2594958d4f4999313641290ad28ebe, <3.14, <=*, <92e53a5274276a7b1ca815b9aacebea4fb7efe75, <=5.15.*, <e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59, 7.3) 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