{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40160 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40160 is a denial of service 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-40160 and fix it if it is affected.\n\nWhat it is: CVE-2025-40160 is a denial of service 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-40160 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-40160/ (Markdown: https://insights.sbomify.com/CVE-2025-40160/index.md)","id":"CVE-2025-40160","markdown":"https://insights.sbomify.com/CVE-2025-40160/index.md","name":"CVE-2025-40160","record":{"aliases":["BELL-CVE-2025-40160","DEBIAN-CVE-2025-40160","GHSA-86vm-hhg5-pm6h","ROOT-OS-DEBIAN-11-CVE-2025-40160","ROOT-OS-DEBIAN-12-CVE-2025-40160","ROOT-OS-DEBIAN-13-CVE-2025-40160","ROOT-OS-UBUNTU-2204-CVE-2025-40160","ROOT-OS-UBUNTU-2404-CVE-2025-40160","UBUNTU-CVE-2025-40160"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel crash by attempting to bind a virtual IRQ to a different CPU than its current binding.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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\nxen/events: Return -EEXIST for bound VIRQs\n\nChange find_virq() to return -EEXIST when a VIRQ is bound to a\ndifferent CPU than the one passed in.  With that, remove the BUG_ON()\nfrom bind_virq_to_irq() to propogate the error upwards.\n\nSome VIRQs are per-cpu, but others are per-domain or global.  Those must\nbe bound to CPU0 and can then migrate elsewhere.  The lookup for\nper-domain and global will probably fail when migrated off CPU 0,\nespecially when the current CPU is tracked.  This now returns -EEXIST\ninstead of BUG_ON().\n\nA second call to bind a per-domain or global VIRQ is not expected, but\nmake it non-fatal to avoid trying to look up the irq, since we don't\nknow which per_cpu(virq_to_irq) it will be in.","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":"xen/events: Return -EEXIST for bound VIRQs","id":"CVE-2025-40160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"mailbox: zynqmp-ipi: Fix SGI cleanup on unbind","id":"CVE-2025-40161"},"packages":[],"prev":{"headline":"xsk: Harden userspace-supplied xdp_desc validation","id":"CVE-2025-40159"},"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-05-11","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel crash by attempting to bind a virtual IRQ to a different CPU than its current binding.","url":"https://insights.sbomify.com/CVE-2025-40160/"}