CVE-2026-90295

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

N/A
Published: September 17, 2026 at 04:08 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.14b4573d1d657aae28bedf3a9a1f5367e09c80d1d6
Vendor states this is fixed in 263a35331169390f7f9ccb51d74e668610199af4 (fixed)
Vendor states this is fixed in 49f2f9b1d0cc76cf221306fc707703205bd27073 (fixed)
Vendor states this is fixed in 55516986a3d81325c84f2d4ae9cd03116bc63599 (fixed)
Vendor states this is fixed in 55864b26c22cbd4b2e0d36154a8c35931c2e133b (fixed)
Vendor states this is fixed in 8c3afcf27fa4582c1ab912503dc8a4ebb8dc0f82 (fixed)
Vendor states this is fixed in aaa66e60c0e21d19993a95bc3718dc29eb2d3192 (fixed)
Vendor states this is fixed in b166bb79b7ef36b4f1d6d1f40d1a72b2eb0a56b9 (fixed)
Vendor states this is fixed in c5135bc34ea37e9d19f758e61ac44415afb3891a (fixed)
Vendor states this is fixed in 3.14 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card