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.

Is your site exposed to CVE-2026-90296?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0022

Probability of exploitation

0.12%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/0f77d1a0a25056146eea1f8619fa06ce287c91f7 https://git.kernel.org/stable/c/22c23c72c3b21fa3ec3db5070dfc0582794e0ef9 https://git.kernel.org/stable/c/38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c https://git.kernel.org/stable/c/493c4d5982f037f288509a1cee352b8b9705fb38 https://git.kernel.org/stable/c/92e53a5274276a7b1ca815b9aacebea4fb7efe75 https://git.kernel.org/stable/c/9e314b3ecd2594958d4f4999313641290ad28ebe https://git.kernel.org/stable/c/d91f07381e2b70578ff92b83d9422ac31e7b9096 https://git.kernel.org/stable/c/e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59

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 do I check if I'm vulnerable to CVE-2026-90296? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.