{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90295 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90295 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-90295 and fix it if it is affected.\n\nWhat it is: CVE-2026-90295 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-90295 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-90295/ (Markdown: https://insights.sbomify.com/CVE-2026-90295/index.md)","id":"CVE-2026-90295","markdown":"https://insights.sbomify.com/CVE-2026-90295/index.md","name":"CVE-2026-90295","record":{"aliases":["AZL-102245","BELL-CVE-2026-90295","DEBIAN-CVE-2026-90295","GHSA-mqwh-wx53-vxj4","UBUNTU-CVE-2026-90295"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A local attacker with root privileges can trigger an out-of-bounds write in the imx6q cpufreq driver by repeatedly binding and unbinding it, potentially leading to code execution or privilege escalation.","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 out-of-bounds write when probed more than once\n\nimx6_soc_volt is allocated fresh on every probe, sized to the number of\nARM OPPs:\n\n\timx6_soc_volt = devm_kcalloc(cpu_dev, num, sizeof(*imx6_soc_volt),\n\t\t\t\t     GFP_KERNEL);\n\nbut it is filled through soc_opp_count, which has static storage and is\nnever reset. A second bind after an unbind keeps indexing from where the\nfirst one stopped, and writes past the end of the new array.\n\nUnbinding and rebinding the driver on qemu's mcimx6ul-evk, under KASAN:\n\n  BUG: KASAN: slab-out-of-bounds in imx6q_cpufreq_probe+0x3b0/0xa34\n  Write of size 4 at addr c5e90480 by task binder/73\n   imx6q_cpufreq_probe from platform_probe+0x88/0xe4\n   platform_probe from really_probe+0x108/0x384\n   bind_store from kernfs_fop_write_iter+0x1b4/0x28c\n\nThe write lands one u32 past the end of the allocation.\n\nsoc_opp_count is only read a few lines below the loop that fills it, so it\nnever needed static storage. Make it a local.","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 out-of-bounds write when probed more than once","id":"CVE-2026-90295","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":"cpufreq: imx6q: fix devres accumulation across driver rebind","id":"CVE-2026-90296"},"packages":[],"prev":{"headline":"IB/isert: delay the final Login Response until the session is registered","id":"CVE-2026-90294"},"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 local attacker with root privileges can trigger an out-of-bounds write in the imx6q cpufreq driver by repeatedly binding and unbinding it, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-90295/"}