{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98770 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98770 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98770 and fix it if it is affected.\n\nWhat it is: CVE-2026-98770 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98770 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-98770/ (Markdown: https://insights.sbomify.com/CVE-2026-98770/index.md)","id":"CVE-2026-98770","markdown":"https://insights.sbomify.com/CVE-2026-98770/index.md","name":"CVE-2026-98770","record":{"aliases":["AZL-109337","BELL-CVE-2026-98770","DEBIAN-CVE-2026-98770","GHSA-2cr9-h7x6-p393","UBUNTU-CVE-2026-98770"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel USB gadget","requires_auth":"none","summary":"A local attacker with physical access can trigger an out-of-bounds write in the Linux kernel USB MIDI2 gadget driver via configfs, potentially leading to code execution or system crash.","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\nusb: gadget: midi2: Fix the jack descriptor array sizes\n\nThe jack in/out descriptor arrays in struct f_midi2_usb_config have\nthe size of MAX_CABLES, which look reasonable -- but it turned out to\nbe incorrect.  Namely, the entries for those arrays are added from\nboth inputs and outputs, hence for each loop cycle, it adds two, ended\nup with as twice as the expected size.  This inconsistency may result\nin potential OOB when a large number of jacks are set up via configfs,\nalthough the max number of cables (the loop count) is limited to\nMAX_CABLES.\n\nFor addressing it, correct the jack_ins \u0026 jack_outs array sizes to\ntwice, MAX_CABLES * 2.","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":"usb: gadget: midi2: Fix the jack descriptor array sizes","id":"CVE-2026-98770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"usb: storage: sierra_ms: reject short SWoC info transfers","id":"CVE-2026-98771"},"packages":[],"prev":{"headline":"usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd","id":"CVE-2026-98769"},"products":["Linux"],"published":"2026-10-18","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-21","vendors":["Linux"]},"summary":"A local attacker with physical access can trigger an out-of-bounds write in the Linux kernel USB MIDI2 gadget driver via configfs, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-98770/"}