{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90095 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90095 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-90095 and fix it if it is affected.\n\nWhat it is: CVE-2026-90095 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-90095 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-90095/ (Markdown: https://insights.sbomify.com/CVE-2026-90095/index.md)","id":"CVE-2026-90095","markdown":"https://insights.sbomify.com/CVE-2026-90095/index.md","name":"CVE-2026-90095","record":{"aliases":["BELL-CVE-2026-90095","DEBIAN-CVE-2026-90095","GHSA-f6c3-623p-967p","UBUNTU-CVE-2026-90095"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel FUSE io-uring implementation can cause deadlocks, leading to denial of service for local users.","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\nfuse: Fix the condition to enable over-io-uring\n\nThe existing condition in fuse_uring_cmd() is there only to avoid\ndisabling io-uring for connections that already run with it, missing\nwas a condition to refuse any IORING_OP_URING_CMD if the\nconnection/channel didn't get enabled because of missing FUSE_INIT\nreply flag FUSE_OVER_IO_URING. Without the reply flag the barrier in\nfuse_uring_ready() doesn't work and IO could already be going on and\ncause deadlock states (at a minimum one between fch-\u003ebg_lock and\nqueue-\u003elock).\n\nThe change itself is trivial, but brings behavior change,\nFUSE_OVER_IO_URING has to be set in the FUSE_INIT_REPLY by fuse servers\nto accept any IORING_OP_URING_CMD. Libfuse does that and the only\nnon-libfuse implementation I found (fractal-fuse) also does it.\nQemu patches for fuse-io-uring are not merged yet, as far as I know.\n\nMoved up is the smp_load_acquire(\u0026fch-\u003einitialized) check, as a\nfuse-server implementation might try to setup io-uring before FUSE_INIT\nis processed and might have gotten -EOPNOTSUPP instead of -EAGAIN.\n\nAlso fixed is a stale comment that explains the handling of the\nFUSE_OVER_IO_URING flag in early RFC versions.\n\nIf there should be a report from any library or application we\nprobably need to revert this commit.","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":"fuse: Fix the condition to enable over-io-uring","id":"CVE-2026-90095","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":"fuse: invalidate the correct range after O_APPEND direct write","id":"CVE-2026-90096"},"packages":[],"prev":{"headline":"arm64: process: Fix context switching MTE store-only tag check","id":"CVE-2026-90094"},"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 FUSE io-uring implementation can cause deadlocks, leading to denial of service for local users.","url":"https://insights.sbomify.com/CVE-2026-90095/"}