Skip to content
Noroxi
CVE-2026-90296· NVD / CVE Program· CNA Linux

cpufreq: imx6q: fix devres accumulation across driver rebind

In the Linux kernel, the following vulnerability has been resolved: cpufreq: imx6q: fix devres accumulation across driver rebind imx6_soc_volt is allocated with devm_kcalloc(cpu_dev, ...), where cpu_dev is the CPU device from get_cpu_device(0). That device is never unbound, so its devres list is never released, and imx6q_cpufreq_remove() does not free the array either. Every probe therefore adds an allocation that stays for the lifetime of the system. Allocate against the platform device instead. Its devres is released when the driver is unbound, which is exactly the lifetime the array wants: imx6q_set_target() reads it, and nothing may reach that after cpufreq_unregister_driver(). That makes the array actually go away on unbind, so also clear the file-scope pointer in remove and on the failed-probe path, rather than leave it pointing at memory devres is about to release. Tested by rebinding the driver on qemu's mcimx6ul-evk.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Sep 17, 2026
EPSS
0.2% · 11th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.14affected
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 493c4d5982f037f288509a1cee352b8b9705fb38affected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before d91f07381e2b70578ff92b83d9422ac31e7b9096affected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 38d2c3c9238b9d499e1829a3b8e80c2f73c73b5caffected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 92e53a5274276a7b1ca815b9aacebea4fb7efe75affected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 9e314b3ecd2594958d4f4999313641290ad28ebeaffected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59affected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 0f77d1a0a25056146eea1f8619fa06ce287c91f7affected · git
    • b4573d1d657aae28bedf3a9a1f5367e09c80d1d6 and later · before 22c23c72c3b21fa3ec3db5070dfc0582794e0ef9affected · git
    • before 3.14not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxall versions—
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0f77d1a0a25056146eea1f8619fa06ce287c91f7Vendor (CNA)
Linux Linux22c23c72c3b21fa3ec3db5070dfc0582794e0ef9Vendor (CNA)
Linux Linux38d2c3c9238b9d499e1829a3b8e80c2f73c73b5cVendor (CNA)
Linux Linux493c4d5982f037f288509a1cee352b8b9705fb38Vendor (CNA)
Linux Linux92e53a5274276a7b1ca815b9aacebea4fb7efe75Vendor (CNA)
Linux Linux9e314b3ecd2594958d4f4999313641290ad28ebeVendor (CNA)
Linux Linuxd91f07381e2b70578ff92b83d9422ac31e7b9096Vendor (CNA)
Linux Linuxe2d2612e63e294ebcdec7c6f08a1a052b7dfdc59Vendor (CNA)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records