{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80900 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80900 is a vulnerability in Linux, published on 4 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-80900 and fix it if it is affected.\n\nWhat it is: CVE-2026-80900 is a vulnerability in Linux, published on 4 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-80900 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-80900/ (Markdown: https://insights.sbomify.com/CVE-2026-80900/index.md)","id":"CVE-2026-80900","markdown":"https://insights.sbomify.com/CVE-2026-80900/index.md","name":"CVE-2026-80900","record":{"aliases":["DEBIAN-CVE-2026-80900","GHSA-6r73-j3jm-8qjg","UBUNTU-CVE-2026-80900"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A flaw in the Linux kernel's ASoC SDCA driver allows bypassing size checks, potentially leading to memory corruption or denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\nASoC: SDCA: Make UMP message size check more robust\n\nIf message offset was larger than the buffer length the size\ncheck will pass incorrectly. Refactor the check such that it is\nmore robust to invalid sizes.","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: SDCA: Make UMP message size check more robust","id":"CVE-2026-80900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ipvs: fix the checksum validations","id":"CVE-2026-80901"},"packages":[],"prev":{"headline":"erofs: remove fscache backend entirely","id":"CVE-2026-80899"},"products":["Linux"],"published":"2026-09-04","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-09-04","vendors":["Linux"]},"summary":"A flaw in the Linux kernel's ASoC SDCA driver allows bypassing size checks, potentially leading to memory corruption or denial of service.","url":"https://insights.sbomify.com/CVE-2026-80900/"}