{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80968 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80968 is a memory corruption vulnerability in Linux, published on 11 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-80968 and fix it if it is affected.\n\nWhat it is: CVE-2026-80968 is a memory corruption vulnerability in Linux, published on 11 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-80968 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-80968/ (Markdown: https://insights.sbomify.com/CVE-2026-80968/index.md)","id":"CVE-2026-80968","markdown":"https://insights.sbomify.com/CVE-2026-80968/index.md","name":"CVE-2026-80968","record":{"aliases":["AZL-100313","BELL-CVE-2026-80968","DEBIAN-CVE-2026-80968","GHSA-x5g7-h5wf-2v48","UBUNTU-CVE-2026-80968"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A missing check in the ALSA mts64 driver allows out-of-bounds access via negative card indices, potentially causing crashes or data leaks.","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\nALSA: mts64: Check card index validity at probe\n\nAlthough mts64 driver has a check of the given devptr-\u003eid value, it\ndoesn't check for a negative id, which is often given as \"none\" or\nsuch value when bound via sysfs.  This may lead to OOB access for\nindex[] and other parameters.\n\nAdd a sanity check for the card index and warn/correct it if it's a\nvalue out of the range.","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":"ALSA: mts64: Check card index validity at probe","id":"CVE-2026-80968","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":"ALSA: mpu401: Check card index validity at probe","id":"CVE-2026-80969"},"packages":[],"prev":{"headline":"ALSA: pcxhr: initialize mutexes before requesting threaded IRQ","id":"CVE-2026-80967"},"products":["Linux"],"published":"2026-09-11","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 missing check in the ALSA mts64 driver allows out-of-bounds access via negative card indices, potentially causing crashes or data leaks.","url":"https://insights.sbomify.com/CVE-2026-80968/"}