{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98450 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98450 is a denial of service vulnerability in Linux, published on 18 Oct 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-98450 and fix it if it is affected.\n\nWhat it is: CVE-2026-98450 is a denial of service vulnerability in Linux, published on 18 Oct 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-98450 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-98450/ (Markdown: https://insights.sbomify.com/CVE-2026-98450/index.md)","id":"CVE-2026-98450","markdown":"https://insights.sbomify.com/CVE-2026-98450/index.md","name":"CVE-2026-98450","record":{"aliases":["AZL-108717","BELL-CVE-2026-98450","DEBIAN-CVE-2026-98450","GHSA-vqm5-qg35-949v","UBUNTU-CVE-2026-98450"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel SMB client","requires_auth":"none","summary":"A flaw in the Linux kernel SMB client fails to close remote handles on compound wait errors, potentially leading to resource exhaustion and denial of service.","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\nsmb: client: close completed creates on compound wait errors\n\ncompound_send_recv() waits for responses in order. If a later wait is\ninterrupted, or if a later MID fails during response synchronization, an\nearlier CREATE may already have opened a remote handle. The earlier mid\nis then released without invoking handle_cancelled_mid(), leaving the\nremote handle open because no FID was copied to the caller.\n\nMark completed earlier mids as cancelled when a compound wait or MID\nsynchronization aborts. Keep their response buffers attached while the\nMIDs are synchronized, and transfer them only after synchronization of\nthe processed responses, so the release path can inspect successful\nCREATE responses and queue SMB2_close() after a later failure. Account for\na remote open only after the close work is allocated and before it is\nqueued, since the caller has not yet updated num_remote_opens. Mark the\ncreate+close compound used by smb2_unlink() so it is not closed again.\nNon-CREATE responses and compounds that already include a close keep their\nexisting behavior.","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":"smb: client: close completed creates on compound wait errors","id":"CVE-2026-98450","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":"smb: client: use finish_no_open() for non-regular inodes","id":"CVE-2026-98451"},"packages":[],"prev":{"headline":"smb: client: delete compound mids on send failure before unlock","id":"CVE-2026-98449"},"products":["Linux"],"published":"2026-10-18","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-21","vendors":["Linux"]},"summary":"A flaw in the Linux kernel SMB client fails to close remote handles on compound wait errors, potentially leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-98450/"}