{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40343 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40343 is a critical vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40343 and fix it if it is affected.\n\nWhat it is: CVE-2025-40343 is a critical vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40343 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-2025-40343/ (Markdown: https://insights.sbomify.com/CVE-2025-40343/index.md)","id":"CVE-2025-40343","markdown":"https://insights.sbomify.com/CVE-2025-40343/index.md","name":"CVE-2025-40343","record":{"aliases":["BELL-CVE-2025-40343","DEBIAN-CVE-2025-40343","GHSA-247j-3qhv-rpc8","ROOT-OS-DEBIAN-11-CVE-2025-40343","ROOT-OS-DEBIAN-12-CVE-2025-40343","ROOT-OS-DEBIAN-13-CVE-2025-40343","ROOT-OS-UBUNTU-2204-CVE-2025-40343","ROOT-OS-UBUNTU-2404-CVE-2025-40343","UBUNTU-CVE-2025-40343"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel nvmet-fc driver allows double scheduling of association deletion, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.","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":"nvmet-fc: avoid scheduling association deletion twice","id":"CVE-2025-40343","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"ASoC: Intel: avs: Disable periods-elapsed work when closing PCM","id":"CVE-2025-40344"},"packages":[],"prev":{"headline":"nvme-fc: use lock accessing port_state and rport state","id":"CVE-2025-40342"},"products":["Linux"],"published":"2025-12-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A race condition in the Linux kernel nvmet-fc driver allows double scheduling of association deletion, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-40343/"}