CVE-2026-90296
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.
How to fix
- Linux Linux493c4d5982f037f288509a1cee352b8b9705fb38, d91f07381e2b70578ff92b83d9422ac31e7b9096, 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, 92e53a5274276a7b1ca815b9aacebea4fb7efe75, 9e314b3ecd2594958d4f4999313641290ad28ebe, e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59, 0f77d1a0a25056146eea1f8619fa06ce287c91f7, 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Linux Linux | b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < 493c4d5982f037f288509a1cee352b8b9705fb38, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < d91f07381e2b70578ff92b83d9422ac31e7b9096, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < 92e53a5274276a7b1ca815b9aacebea4fb7efe75, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < 9e314b3ecd2594958d4f4999313641290ad28ebe, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < 0f77d1a0a25056146eea1f8619fa06ce287c91f7, b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 ≤ v < 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, 3.14 | 493c4d5982f037f288509a1cee352b8b9705fb38, d91f07381e2b70578ff92b83d9422ac31e7b9096, 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c, 92e53a5274276a7b1ca815b9aacebea4fb7efe75, 9e314b3ecd2594958d4f4999313641290ad28ebe, e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59, 0f77d1a0a25056146eea1f8619fa06ce287c91f7, 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.