{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64243 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64243 is a high-severity vulnerability in Linux kernel, published on 24 Jul 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-64243 and fix it if it is affected.\n\nWhat it is: CVE-2026-64243 is a high-severity vulnerability in Linux kernel, published on 24 Jul 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-64243 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-64243/ (Markdown: https://insights.sbomify.com/CVE-2026-64243/index.md)","id":"CVE-2026-64243","markdown":"https://insights.sbomify.com/CVE-2026-64243/index.md","name":"CVE-2026-64243","record":{"aliases":["BELL-CVE-2026-64243","DEBIAN-CVE-2026-64243","GHSA-g8x3-7685-9cvh","ROOT-OS-UBUNTU-2204-CVE-2026-64243","UBUNTU-CVE-2026-64243"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel audio codec","requires_auth":"low_privilege","summary":"An integer overflow in the Linux kernel's simple-mux codec allows invalid enum values, potentially leading to out-of-bounds reads and code execution.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nASoC: codecs: simple-mux: Fix enum control bounds check\n\nsimple_mux_control_put() rejects values greater than e-\u003eitems, but\nenum control values are zero based. For the two-entry mux used by this\ndriver, valid values are 0 and 1, so value 2 must be rejected as well.\n\nAccepting e-\u003eitems can store an invalid mux state, pass it to the GPIO\nsetter, and pass it on to the DAPM mux update path where it is used as\nan index into the enum text array.\n\nUse the same \u003e= e-\u003eitems check used by the ASoC enum helpers.","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":"ASoC: codecs: simple-mux: Fix enum control bounds check","id":"CVE-2026-64243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"drivers/base/memory: set mem-\u003ealtmap after successful device registration","id":"CVE-2026-64244"},"packages":[],"prev":{"headline":"usb: gadget: net2280: Fix double free in probe error path","id":"CVE-2026-64242"},"products":["Linux"],"published":"2026-07-24","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An integer overflow in the Linux kernel's simple-mux codec allows invalid enum values, potentially leading to out-of-bounds reads and code execution.","url":"https://insights.sbomify.com/CVE-2026-64243/"}