{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93097 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93097 is a denial of service 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-93097 and fix it if it is affected.\n\nWhat it is: CVE-2026-93097 is a denial of service 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-93097 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-93097/ (Markdown: https://insights.sbomify.com/CVE-2026-93097/index.md)","id":"CVE-2026-93097","markdown":"https://insights.sbomify.com/CVE-2026-93097/index.md","name":"CVE-2026-93097","record":{"aliases":["AZL-102980","BELL-CVE-2026-93097","DEBIAN-CVE-2026-93097","GHSA-x7w4-f354-q3xf","UBUNTU-CVE-2026-93097"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A malicious CXL device can cause a kernel hang by returning empty poison lists, blocking system operations.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\ncxl/mbox: Break poison list loop on an empty payload\n\nA device that returns count == 0 with CXL_POISON_FLAG_MORE set on every\niteration never advances nr_records, so the max_errors guard never\ntrips and the do/while loops forever while holding poison.mutex. That\nhangs the sysfs-triggered scan thread and blocks all subsequent poison\noperations on the device. The existing \"Protect against an uncleared\n_FLAG_MORE\" guard was intended to bound a misbehaving device but does\nnot cover the count == 0 case.\n\nStop the loop on an empty payload so a malfunctioning or malicious\ndevice cannot wedge the poison scan.","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":"cxl/mbox: Break poison list loop on an empty payload","id":"CVE-2026-93097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"rpmsg: glink: fix deadlock in endpoint destroy during driver detach","id":"CVE-2026-93098"},"packages":[],"prev":{"headline":"cxl/features: Serialize multi-part Get/Set Feature transfers","id":"CVE-2026-93096"},"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 malicious CXL device can cause a kernel hang by returning empty poison lists, blocking system operations.","url":"https://insights.sbomify.com/CVE-2026-93097/"}