{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90034 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90034 is a vulnerability in Linux, published on 16 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-90034 and fix it if it is affected.\n\nWhat it is: CVE-2026-90034 is a vulnerability in Linux, published on 16 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-90034 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-90034/ (Markdown: https://insights.sbomify.com/CVE-2026-90034/index.md)","id":"CVE-2026-90034","markdown":"https://insights.sbomify.com/CVE-2026-90034/index.md","name":"CVE-2026-90034","record":{"aliases":["AZL-101322","BELL-CVE-2026-90034","DEBIAN-CVE-2026-90034","GHSA-cc2m-7vjr-3594","UBUNTU-CVE-2026-90034"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB driver","requires_auth":"none","summary":"A local attacker with physical access can read uninitialized kernel memory via the mdc800 USB image driver due to missing buffer zeroing.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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: image: mdc800: change kmalloc() to kzalloc()\n\nChange the kmalloc() calls in usb_mdc800_init() for irq_urb_buffer and\ndownload_urb_buffer to kzalloc(), avoiding potential stack leaks if a\nshorter message is received in mdc800_usb_irq() and\nmdc800_usb_download_notify()","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: image: mdc800: change kmalloc() to kzalloc()","id":"CVE-2026-90034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"drm/amd/display: fix division by zero in get_estimated_bw()","id":"CVE-2026-90035"},"packages":[],"prev":{"headline":"ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output()","id":"CVE-2026-90033"},"products":["Linux"],"published":"2026-09-16","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 physical access can read uninitialized kernel memory via the mdc800 USB image driver due to missing buffer zeroing.","url":"https://insights.sbomify.com/CVE-2026-90034/"}