CVE-2026-90296

Unknown

Last modified

CVE-2026-90296 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < 493c4d5982f037f288509a1cee352b8b9705fb38; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < d91f07381e2b70578ff92b83d9422ac31e7b9096; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < 92e53a5274276a7b1ca815b9aacebea4fb7efe75; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < 9e314b3ecd2594958d4f4999313641290ad28ebe; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < 0f77d1a0a25056146eea1f8619fa06ce287c91f7; >= b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, < 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9
LinuxLinux3.14

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90296?
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 severe is CVE-2026-90296?
Severity scoring for CVE-2026-90296 is pending analysis.
How do I fix CVE-2026-90296?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-90296?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST