Kernel memory corruption via stale driver-probe counter
Published Sep 17, 2026 · Updated Sep 17, 2026
Out-of-bounds writes in Linux imx6q cpufreq allow local users to corrupt kernel memory by unbinding and rebinding the driver. The imx6q_cpufreq_probe function retains the static soc_opp_count across probes and uses it to index a newly allocated imx6_soc_volt array, writing four bytes beyond its end. Triggering requires administrative driver-binding access on an affected i.MX6 system; the published reproduction demonstrates a kernel heap overwrite, not privilege escalation or arbitrary code execution.
Summary
What happened
Out-of-bounds writes in Linux imx6q cpufreq allow local users to corrupt kernel memory by unbinding and rebinding the driver. The imx6q_cpufreq_probe function retains the static soc_opp_count across probes and uses it to index a newly allocated imx6_soc_volt array, writing four bytes beyond its end. Triggering requires administrative driver-binding access on an affected i.MX6 system; the published reproduction demonstrates a kernel heap overwrite, not privilege escalation or arbitrary code execution.
The record
- CVE
- CVE-2026-90295
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.14
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <263a35331169390f7f9ccb51d74e668610199af4
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <49f2f9b1d0cc76cf221306fc707703205bd27073
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <55516986a3d81325c84f2d4ae9cd03116bc63599
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <55864b26c22cbd4b2e0d36154a8c35931c2e133b
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <8c3afcf27fa4582c1ab912503dc8a4ebb8dc0f82
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <aaa66e60c0e21d19993a95bc3718dc29eb2d3192
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <b166bb79b7ef36b4f1d6d1f40d1a72b2eb0a56b9
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <c5135bc34ea37e9d19f758e61ac44415afb3891a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started