{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93118 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93118 is a vulnerability in Linux, published on 17 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-93118 and fix it if it is affected.\n\nWhat it is: CVE-2026-93118 is a vulnerability in Linux, published on 17 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-93118 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-93118/ (Markdown: https://insights.sbomify.com/CVE-2026-93118/index.md)","id":"CVE-2026-93118","markdown":"https://insights.sbomify.com/CVE-2026-93118/index.md","name":"CVE-2026-93118","record":{"aliases":["AZL-102150","BELL-CVE-2026-93118","DEBIAN-CVE-2026-93118","GHSA-m596-7j6r-7chf","UBUNTU-CVE-2026-93118"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel USB driver","requires_auth":"none","summary":"A missing check for DMA allocation failure in the Aspeed UDC driver causes a null pointer dereference during probe, leading to a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: aspeed_udc: check endpoint DMA allocation\n\nast_udc_probe() allocates a coherent DMA buffer used as the backing store\nfor endpoint buffers. ast_udc_init_ep() derives per-endpoint buffer\npointers from udc-\u003eep0_buf, so a failed allocation is dereferenced during\nprobe.\n\nCheck the allocation before endpoint setup. The existing probe error path\ncalled ast_udc_remove(), which unregisters the gadget unconditionally and\nis not safe before usb_add_gadget_udc() succeeds. Add a local cleanup\nhelper for probe failures so pre-registration failures only unwind the\nresources that were actually initialized.\n\nThis was found by a local static analysis checker for unchecked allocator\nreturns while scanning Linux 6.16. The change was checked by applying it\nto current mainline and by running checkpatch. I do not have access to\nAspeed UDC hardware, so no runtime testing was performed.","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: aspeed_udc: check endpoint DMA allocation","id":"CVE-2026-93118","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"usb: ljca: bound bank_num in ljca_enumerate_gpio()","id":"CVE-2026-93119"},"packages":[],"prev":{"headline":"usb: fix UAF when probe runs concurrent to dyn ID removal","id":"CVE-2026-93117"},"products":["Linux"],"published":"2026-09-17","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 for DMA allocation failure in the Aspeed UDC driver causes a null pointer dereference during probe, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-93118/"}