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

Not scored Published Updated

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.

Exploited in the wild
Not known
Login needed
An administrator
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

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.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-90295 being exploited?

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

Sources

Also known as AZL-102245, BELL-CVE-2026-90295, DEBIAN-CVE-2026-90295, GHSA-mqwh-wx53-vxj4, UBUNTU-CVE-2026-90295.

Is CVE-2026-90295 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free