{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40330 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40330 is a memory corruption vulnerability in Linux, published on 9 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-40330 and fix it if it is affected.\n\nWhat it is: CVE-2025-40330 is a memory corruption vulnerability in Linux, published on 9 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-40330 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-40330/ (Markdown: https://insights.sbomify.com/CVE-2025-40330/index.md)","id":"CVE-2025-40330","markdown":"https://insights.sbomify.com/CVE-2025-40330/index.md","name":"CVE-2025-40330","record":{"aliases":["BELL-CVE-2025-40330","DEBIAN-CVE-2025-40330","GHSA-fj8r-2x4x-2q83","UBUNTU-CVE-2025-40330"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the bnxt_en driver allows memory corruption during kexec, potentially leading to denial of service or code execution in the new kernel.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nbnxt_en: Shutdown FW DMA in bnxt_shutdown()\n\nThe netif_close() call in bnxt_shutdown() only stops packet DMA.  There\nmay be FW DMA for trace logging (recently added) that will continue.  If\nwe kexec to a new kernel, the DMA will corrupt memory in the new kernel.\n\nAdd bnxt_hwrm_func_drv_unrgtr() to unregister the driver from the FW.\nThis will stop the FW DMA.  In case the call fails, call pcie_flr() to\nreset the function and stop the DMA.","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":"bnxt_en: Shutdown FW DMA in bnxt_shutdown()","id":"CVE-2025-40330","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"sctp: Prevent TOCTOU out-of-bounds write","id":"CVE-2025-40331"},"packages":[],"prev":{"headline":"drm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb","id":"CVE-2025-40329"},"products":["Linux"],"published":"2025-12-09","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-05-11","vendors":["Linux"]},"summary":"A flaw in the bnxt_en driver allows memory corruption during kexec, potentially leading to denial of service or code execution in the new kernel.","url":"https://insights.sbomify.com/CVE-2025-40330/"}