CVE-2026-90296

published 17 Sep 2026 · updated 19 Oct 2026

cpufreq: imx6q: fix devres accumulation across driver rebind

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0f77d1a0a25056146eea1f8619fa06ce287c91f7, Kernel 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, Kernel 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c and 5 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.14, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <0f77d1a0a25056146eea1f8619fa06ce287c91f7, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <493c4d5982f037f288509a1cee352b8b9705fb38, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <92e53a5274276a7b1ca815b9aacebea4fb7efe75, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <9e314b3ecd2594958d4f4999313641290ad28ebe, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <d91f07381e2b70578ff92b83d9422ac31e7b9096, >=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <e2d2612e63e294ebcdec7c6f08a1a052b7dfdc590f77d1a0a25056146eea1f8619fa06ce287c91f7, 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, 493c4d5982f037f288509a1cee352b8b9705fb38, 92e53a5274276a7b1ca815b9aacebea4fb7efe75, 9e314b3ecd2594958d4f4999313641290ad28ebe, d91f07381e2b70578ff92b83d9422ac31e7b9096, e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-90296 severity on Zeptric[![CVE-2026-90296](https://zeptric.io/badge/cve/CVE-2026-90296.svg)](https://zeptric.io/cve/CVE-2026-90296)