{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40180 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40180 is a memory corruption vulnerability in Linux, published on 12 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-40180 and fix it if it is affected.\n\nWhat it is: CVE-2025-40180 is a memory corruption vulnerability in Linux, published on 12 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-40180 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-40180/ (Markdown: https://insights.sbomify.com/CVE-2025-40180/index.md)","id":"CVE-2025-40180","markdown":"https://insights.sbomify.com/CVE-2025-40180/index.md","name":"CVE-2025-40180","record":{"aliases":["AZL-70064","BELL-CVE-2025-40180","DEBIAN-CVE-2025-40180","GHSA-78x4-5hh5-f94g","ROOT-OS-DEBIAN-11-CVE-2025-40180","ROOT-OS-DEBIAN-12-CVE-2025-40180","ROOT-OS-DEBIAN-13-CVE-2025-40180","ROOT-OS-UBUNTU-2204-CVE-2025-40180","ROOT-OS-UBUNTU-2404-CVE-2025-40180","UBUNTU-CVE-2025-40180"],"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":"Out-of-bounds access in the ZynqMP IPI mailbox driver cleanup loop can lead to memory corruption and potential system crashes or code execution.","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\nmailbox: zynqmp-ipi: Fix out-of-bounds access in mailbox cleanup loop\n\nThe cleanup loop was starting at the wrong array index, causing\nout-of-bounds access.\nStart the loop at the correct index for zero-indexed arrays to prevent\naccessing memory beyond the allocated array bounds.","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":"mailbox: zynqmp-ipi: Fix out-of-bounds access in mailbox cleanup loop","id":"CVE-2025-40180","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":"x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP","id":"CVE-2025-40181"},"packages":[],"prev":{"headline":"ext4: verify orphan file size is not too big","id":"CVE-2025-40179"},"products":["Linux"],"published":"2025-11-12","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":"Out-of-bounds access in the ZynqMP IPI mailbox driver cleanup loop can lead to memory corruption and potential system crashes or code execution.","url":"https://insights.sbomify.com/CVE-2025-40180/"}