CVE-2026-90296: cpufreq: imx6q: fix devres accumulation across driver rebind
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 0f77d1a0a25056146eea1f8619fa06ce287c91f7, 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c.
Low priority for now. Upgrade to Linux Linux 0f77d1a0a25056146eea1f8619fa06ce287c91f7, 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9, 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.14affected
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 493c4d5982f037f288509a1cee352b8b9705fb38affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before d91f07381e2b70578ff92b83d9422ac31e7b9096affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5caffected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 92e53a5274276a7b1ca815b9aacebea4fb7efe75affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 9e314b3ecd2594958d4f4999313641290ad28ebeaffected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 0f77d1a0a25056146eea1f8619fa06ce287c91f7affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9affected · git
- before 3.14not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90294Sep 17, 2026 · IB/isert: delay the final Login Response until the session is registered30Monitor
- ← EarlierCVE-2026-90295Sep 17, 2026 · cpufreq: imx6q: fix out-of-bounds write when probed more than once0Monitor
- Later →CVE-2026-90297Sep 17, 2026 · drm/sun4i: crtc: Propagate layer initialization error0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f77d1a0a25056146eea1f8619fa06ce287c91f7 | Vendor (CNA) |
| Linux Linux | 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9 | Vendor (CNA) |
| Linux Linux | 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c | Vendor (CNA) |
| Linux Linux | 493c4d5982f037f288509a1cee352b8b9705fb38 | Vendor (CNA) |
| Linux Linux | 92e53a5274276a7b1ca815b9aacebea4fb7efe75 | Vendor (CNA) |
| Linux Linux | 9e314b3ecd2594958d4f4999313641290ad28ebe | Vendor (CNA) |
| Linux Linux | d91f07381e2b70578ff92b83d9422ac31e7b9096 | Vendor (CNA) |
| Linux Linux | e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/22c23c72c3b21fa3ec3db5070dfc0582794e0ef9
- git.kernel.org/stable/c/38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c
- git.kernel.org/stable/c/493c4d5982f037f288509a1cee352b8b9705fb38
- git.kernel.org/stable/c/92e53a5274276a7b1ca815b9aacebea4fb7efe75
- git.kernel.org/stable/c/9e314b3ecd2594958d4f4999313641290ad28ebe
- git.kernel.org/stable/c/d91f07381e2b70578ff92b83d9422ac31e7b9096
- git.kernel.org/stable/c/e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59
Vendor advisories and official records. Exploit/PoC links are deliberately left out.