{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93096 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93096 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-93096 and fix it if it is affected.\n\nWhat it is: CVE-2026-93096 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-93096 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-93096/ (Markdown: https://insights.sbomify.com/CVE-2026-93096/index.md)","id":"CVE-2026-93096","markdown":"https://insights.sbomify.com/CVE-2026-93096/index.md","name":"CVE-2026-93096","record":{"aliases":["BELL-CVE-2026-93096","DEBIAN-CVE-2026-93096","GHSA-gqcj-fh23-47rq","UBUNTU-CVE-2026-93096"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel CXL feature handling allows concurrent transfers to corrupt device state, potentially causing denial of service or data corruption.","user_interaction":"not_required","vuln_class":"race_condition"},"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/features: Serialize multi-part Get/Set Feature transfers\n\nA Get or Set Feature payload larger than the mailbox payload size is\nsplit into several mailbox commands. mbox_mutex only serializes\nindividual mailbox commands and is dropped between iterations of these\nloops. Nothing serializes the multi-part transfer as a whole.\ncxl_get_feature() and cxl_set_feature() are reachable concurrently\nfrom fwctl (per-fd RPCs run under a read-held registration lock) and\nfrom the EDAC scrub/ECS/repair paths, so two transfers to the same\nmailbox can interleave their parts and corrupt the device's transfer\ncontext.\n\nAdd a per-mailbox feat_mutex and hold it across the whole transfer in\nboth functions. It nests outside mbox_mutex (which is taken inside\ncxl_internal_send_cmd()), and is taken nowhere else, so no lock-ordering\ninversion is introduced.","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/features: Serialize multi-part Get/Set Feature transfers","id":"CVE-2026-93096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"cxl/mbox: Break poison list loop on an empty payload","id":"CVE-2026-93097"},"packages":[],"prev":{"headline":"hfsplus: validate thread record before delete key rebuild","id":"CVE-2026-93095"},"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 race condition in the Linux kernel CXL feature handling allows concurrent transfers to corrupt device state, potentially causing denial of service or data corruption.","url":"https://insights.sbomify.com/CVE-2026-93096/"}