GHSA-RFCG-VQG6-9MFP
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-90296"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:26Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq: imx6q: fix devres accumulation across driver rebind\n\nimx6_soc_volt is allocated with devm_kcalloc(cpu_dev, ...), where cpu_dev\nis the CPU device from get_cpu_device(0). That device is never unbound, so\nits devres list is never released, and imx6q_cpufreq_remove() does not free\nthe array either. Every probe therefore adds an allocation that stays for\nthe lifetime of the system.\n\nAllocate against the platform device instead. Its devres is released when\nthe driver is unbound, which is exactly the lifetime the array wants:\nimx6q_set_target() reads it, and nothing may reach that after\ncpufreq_unregister_driver().\n\nThat makes the array actually go away on unbind, so also clear the\nfile-scope pointer in remove and on the failed-probe path, rather than\nleave it pointing at memory devres is about to release.\n\nTested by rebinding the driver on qemu\u0027s mcimx6ul-evk.",
"id": "GHSA-rfcg-vqg6-9mfp",
"modified": "2026-09-17T18:31:59Z",
"published": "2026-09-17T18:31:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90296"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0f77d1a0a25056146eea1f8619fa06ce287c91f7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/22c23c72c3b21fa3ec3db5070dfc0582794e0ef9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/38d2c3c9238b9d499e1829a3b8e80c2f73c73b5c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/493c4d5982f037f288509a1cee352b8b9705fb38"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/92e53a5274276a7b1ca815b9aacebea4fb7efe75"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9e314b3ecd2594958d4f4999313641290ad28ebe"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d91f07381e2b70578ff92b83d9422ac31e7b9096"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e2d2612e63e294ebcdec7c6f08a1a052b7dfdc59"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.