CVE-2026-90295: cpufreq: imx6q: fix out-of-bounds write when probed more than once
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 263a35331169390f7f9ccb51d74e668610199af4, 49f2f9b1d0cc76cf221306fc707703205bd27073, 55516986a3d81325c84f2d4ae9cd03116bc63599; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 263a35331169390f7f9ccb51d74e668610199af4, 49f2f9b1d0cc76cf221306fc707703205bd27073, 55516986a3d81325c84f2d4ae9cd03116bc63599; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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 out-of-bounds write when probed more than once imx6_soc_volt is allocated fresh on every probe, sized to the number of ARM OPPs: imx6_soc_volt = devm_kcalloc(cpu_dev, num, sizeof(*imx6_soc_volt), GFP_KERNEL); but it is filled through soc_opp_count, which has static storage and is never reset. A second bind after an unbind keeps indexing from where the first one stopped, and writes past the end of the new array. Unbinding and rebinding the driver on qemu's mcimx6ul-evk, under KASAN: BUG: KASAN: slab-out-of-bounds in imx6q_cpufreq_probe+0x3b0/0xa34 Write of size 4 at addr c5e90480 by task binder/73 imx6q_cpufreq_probe from platform_probe+0x88/0xe4 platform_probe from really_probe+0x108/0x384 bind_store from kernfs_fop_write_iter+0x1b4/0x28c The write lands one u32 past the end of the allocation. soc_opp_count is only read a few lines below the loop that fills it, so it never needed static storage. Make it a local.
- 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 263a35331169390f7f9ccb51d74e668610199af4affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 49f2f9b1d0cc76cf221306fc707703205bd27073affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before c5135bc34ea37e9d19f758e61ac44415afb3891aaffected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 55864b26c22cbd4b2e0d36154a8c35931c2e133baffected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before b166bb79b7ef36b4f1d6d1f40d1a72b2eb0a56b9affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before aaa66e60c0e21d19993a95bc3718dc29eb2d3192affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 55516986a3d81325c84f2d4ae9cd03116bc63599affected · git
- b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 8c3afcf27fa4582c1ab912503dc8a4ebb8dc0f82affected · 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-90293Sep 17, 2026 · IB/isert: post the full-feature receive buffers after session registration30Monitor
- ← EarlierCVE-2026-90294Sep 17, 2026 · IB/isert: delay the final Login Response until the session is registered30Monitor
- Later →CVE-2026-90296Sep 17, 2026 · cpufreq: imx6q: fix devres accumulation across driver rebind0Monitor
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 | 263a35331169390f7f9ccb51d74e668610199af4 | Vendor (CNA) |
| Linux Linux | 49f2f9b1d0cc76cf221306fc707703205bd27073 | Vendor (CNA) |
| Linux Linux | 55516986a3d81325c84f2d4ae9cd03116bc63599 | Vendor (CNA) |
| Linux Linux | 55864b26c22cbd4b2e0d36154a8c35931c2e133b | Vendor (CNA) |
| Linux Linux | 8c3afcf27fa4582c1ab912503dc8a4ebb8dc0f82 | Vendor (CNA) |
| Linux Linux | aaa66e60c0e21d19993a95bc3718dc29eb2d3192 | Vendor (CNA) |
| Linux Linux | b166bb79b7ef36b4f1d6d1f40d1a72b2eb0a56b9 | Vendor (CNA) |
| Linux Linux | c5135bc34ea37e9d19f758e61ac44415afb3891a | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| 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/49f2f9b1d0cc76cf221306fc707703205bd27073
- git.kernel.org/stable/c/55516986a3d81325c84f2d4ae9cd03116bc63599
- git.kernel.org/stable/c/55864b26c22cbd4b2e0d36154a8c35931c2e133b
- git.kernel.org/stable/c/8c3afcf27fa4582c1ab912503dc8a4ebb8dc0f82
- git.kernel.org/stable/c/aaa66e60c0e21d19993a95bc3718dc29eb2d3192
- git.kernel.org/stable/c/b166bb79b7ef36b4f1d6d1f40d1a72b2eb0a56b9
- git.kernel.org/stable/c/c5135bc34ea37e9d19f758e61ac44415afb3891a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.