{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40213 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40213 is a high-severity memory corruption vulnerability in Linux, published on 24 Nov 2025. 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-2025-40213 and fix it if it is affected.\n\nWhat it is: CVE-2025-40213 is a high-severity memory corruption vulnerability in Linux, published on 24 Nov 2025. 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-2025-40213 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-40213/ (Markdown: https://insights.sbomify.com/CVE-2025-40213/index.md)","id":"CVE-2025-40213","markdown":"https://insights.sbomify.com/CVE-2025-40213/index.md","name":"CVE-2025-40213","record":{"aliases":["AZL-89667","BELL-CVE-2025-40213","DEBIAN-CVE-2025-40213","GHSA-hxj9-5m9x-pxq2","ROOT-OS-DEBIAN-13-CVE-2025-40213","UBUNTU-CVE-2025-40213"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel Bluetooth","requires_auth":"low_privilege","summary":"A memory corruption flaw in the Linux kernel Bluetooth subsystem allows attackers to cause a system crash via stack-out-of-bounds writes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\nBluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete\n\nThere is a BUG: KASAN: stack-out-of-bounds in set_mesh_sync due to\nmemcpy from badly declared on-stack flexible array.\n\nAnother crash is in set_mesh_complete() due to double list_del via\nmgmt_pending_valid + mgmt_pending_remove.\n\nUse DEFINE_FLEX to declare the flexible array right, and don't memcpy\noutside bounds.\n\nAs mgmt_pending_valid removes the cmd from list, use mgmt_pending_free,\nand also report status on error.","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":"Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete","id":"CVE-2025-40213","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"af_unix: Initialise scc_index in unix_add_edge().","id":"CVE-2025-40214"},"packages":[],"prev":{"headline":"nfsd: fix refcount leak in nfsd_set_fh_dentry()","id":"CVE-2025-40212"},"products":["Linux"],"published":"2025-11-24","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A memory corruption flaw in the Linux kernel Bluetooth subsystem allows attackers to cause a system crash via stack-out-of-bounds writes.","url":"https://insights.sbomify.com/CVE-2025-40213/"}