CVE-2026-90296cpufreq: imx6q: fix devres accumulation across driver rebind
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 493c4d5982f037f288509a1cee352b8b9705fb38
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < d91f07381e2b70578ff92b83d9422ac31e7b9096
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 92e53a5274276a7b1ca815b9aacebea4fb7efe75
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 9e314b3ecd2594958d4f4999313641290ad28ebe
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 0f77d1a0a25056146eea1f8619fa06ce287c91f7
- affected b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 – < 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9
- affected 3.14
- unaffected < 3.14
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.110 – ≤ 6.12.*
- unaffected 6.18.52 – ≤ 6.18.*
- unaffected 7.2.6 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/493c4d5982f037f288509a1cee352b8b9705fb38 (opens in a new tab)
- https://git.kernel.org/stable/c/d91f07381e2b70578ff92b83d9422ac31e7b9096 (opens in a new tab)
- https://git.kernel.org/stable/c/38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c (opens in a new tab)
- https://git.kernel.org/stable/c/92e53a5274276a7b1ca815b9aacebea4fb7efe75 (opens in a new tab)
- https://git.kernel.org/stable/c/9e314b3ecd2594958d4f4999313641290ad28ebe (opens in a new tab)
- https://git.kernel.org/stable/c/e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59 (opens in a new tab)
- https://git.kernel.org/stable/c/0f77d1a0a25056146eea1f8619fa06ce287c91f7 (opens in a new tab)
- https://git.kernel.org/stable/c/22c23c72c3b21fa3ec3db5070dfc0582794e0ef9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81889 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90296)Record last updated .