Memory exhaustion via persistent driver-rebind allocations
Published Sep 17, 2026 · Updated Sep 17, 2026
Memory leakage in Linux Kernel's imx6q cpufreq driver allows local users to consume kernel memory through repeated driver rebinding. The driver allocates imx6_soc_volt against the persistent CPU device, and imx6q_cpufreq_remove() never releases it, retaining another allocation after each probe. Exploitation requires access sufficient to rebind the driver on a system using it; accumulated memory consumption leads to instability or unresponsiveness rather than data disclosure or privilege escalation.
Summary
What happened
Memory leakage in Linux Kernel's imx6q cpufreq driver allows local users to consume kernel memory through repeated driver rebinding. The driver allocates imx6_soc_volt against the persistent CPU device, and imx6q_cpufreq_remove() never releases it, retaining another allocation after each probe. Exploitation requires access sufficient to rebind the driver on a system using it; accumulated memory consumption leads to instability or unresponsiveness rather than data disclosure or privilege escalation.
The record
- CVE
- CVE-2026-90296
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Linux Foundation
- Product
- Linux Kernel
- Classifications
- CWE-772, T1499
- Attack vector
- local
- Privileges
- Unavailable
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 <0f77d1a0a25056146eea1f8619fa06ce287c91f7
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <22c23c72c3b21fa3ec3db5070dfc0582794e0ef9
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <493c4d5982f037f288509a1cee352b8b9705fb38
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <92e53a5274276a7b1ca815b9aacebea4fb7efe75
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <9e314b3ecd2594958d4f4999313641290ad28ebe
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <d91f07381e2b70578ff92b83d9422ac31e7b9096
- Affected versionversion=b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 <e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59
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
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