# CVE-2026-90295: cpufreq: imx6q: fix out-of-bounds write when probed more than once

> A local attacker with root privileges can trigger an out-of-bounds write in the imx6q cpufreq driver by repeatedly binding and unbinding it, potentially leading to code execution or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102245, BELL-CVE-2026-90295, DEBIAN-CVE-2026-90295, GHSA-mqwh-wx53-vxj4, UBUNTU-CVE-2026-90295

## What is CVE-2026-90295?

CVE-2026-90295 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-90295?


## How do I fix CVE-2026-90295?

Apply the vendor's patch.

## Is CVE-2026-90295 being exploited?

There is no known exploitation of CVE-2026-90295 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90295 and fix it if it is affected.

What it is: CVE-2026-90295 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90295 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90295/ (Markdown: https://insights.sbomify.com/CVE-2026-90295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90295
- OSV: https://osv.dev/vulnerability/CVE-2026-90295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90295/
Summaries are generated and may contain mistakes; the official description above is the record.