{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90296 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90296 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90296 and fix it if it is affected.\n\nWhat it is: CVE-2026-90296 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90296 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90296/ (Markdown: https://insights.sbomify.com/CVE-2026-90296/index.md)","id":"CVE-2026-90296","markdown":"https://insights.sbomify.com/CVE-2026-90296/index.md","name":"CVE-2026-90296","record":{"aliases":["AZL-102461","BELL-CVE-2026-90296","DEBIAN-CVE-2026-90296","GHSA-rfcg-vqg6-9mfp","UBUNTU-CVE-2026-90296"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A memory leak in the imx6q cpufreq driver causes resource exhaustion during repeated driver rebinds, leading to denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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's mcimx6ul-evk.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"cpufreq: imx6q: fix devres accumulation across driver rebind","id":"CVE-2026-90296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"drm/sun4i: crtc: Propagate layer initialization error","id":"CVE-2026-90297"},"packages":[],"prev":{"headline":"cpufreq: imx6q: fix out-of-bounds write when probed more than once","id":"CVE-2026-90295"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A memory leak in the imx6q cpufreq driver causes resource exhaustion during repeated driver rebinds, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-90296/"}