{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40301 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40301 is a high-severity vulnerability in Linux, published on 8 Dec 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-40301 and fix it if it is affected.\n\nWhat it is: CVE-2025-40301 is a high-severity vulnerability in Linux, published on 8 Dec 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-40301 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-40301/ (Markdown: https://insights.sbomify.com/CVE-2025-40301/index.md)","id":"CVE-2025-40301","markdown":"https://insights.sbomify.com/CVE-2025-40301/index.md","name":"CVE-2025-40301","record":{"aliases":["BELL-CVE-2025-40301","DEBIAN-CVE-2025-40301","GHSA-mp66-rx49-f278","ROOT-OS-DEBIAN-12-CVE-2025-40301","ROOT-OS-DEBIAN-13-CVE-2025-40301","ROOT-OS-UBUNTU-2404-CVE-2025-40301","UBUNTU-CVE-2025-40301"],"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":"none","summary":"A missing length check in the Linux kernel Bluetooth driver allows attackers to trigger a null dereference, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u003edata contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u003edata[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u003elen before using skb-\u003edata.","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: hci_event: validate skb length for unknown CC opcode","id":"CVE-2025-40301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"media: videobuf2: forbid remove_bufs when legacy fileio is active","id":"CVE-2025-40302"},"packages":[],"prev":{"headline":"x86/vmscape: Add conditional IBPB mitigation","id":"CVE-2025-40300"},"products":["Linux"],"published":"2025-12-08","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-08-05","vendors":["Linux"]},"summary":"A missing length check in the Linux kernel Bluetooth driver allows attackers to trigger a null dereference, causing a system crash.","url":"https://insights.sbomify.com/CVE-2025-40301/"}