{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40020 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40020 is a vulnerability in Linux, published on 24 Oct 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-40020 and fix it if it is affected.\n\nWhat it is: CVE-2025-40020 is a vulnerability in Linux, published on 24 Oct 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-40020 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-40020/ (Markdown: https://insights.sbomify.com/CVE-2025-40020/index.md)","id":"CVE-2025-40020","markdown":"https://insights.sbomify.com/CVE-2025-40020/index.md","name":"CVE-2025-40020","record":{"aliases":["AZL-68808","BELL-CVE-2025-40020","DEBIAN-CVE-2025-40020","GHSA-577q-2j8x-rg25","ROOT-OS-DEBIAN-11-CVE-2025-40020","ROOT-OS-DEBIAN-12-CVE-2025-40020","ROOT-OS-DEBIAN-13-CVE-2025-40020","ROOT-OS-UBUNTU-2404-CVE-2025-40020","UBUNTU-CVE-2025-40020"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A shift-out-of-bounds error in the Linux kernel peak_usb CAN driver can cause a denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\ncan: peak_usb: fix shift-out-of-bounds issue\n\nExplicitly uses a 64-bit constant when the number of bits used for its\nshifting is 32 (which is the case for PC CAN FD interfaces supported by\nthis driver).\n\n[mkl: update subject, apply manually]","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":"can: peak_usb: fix shift-out-of-bounds issue","id":"CVE-2025-40020","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"tracing: dynevent: Add a missing lockdown check on dynevent","id":"CVE-2025-40021"},"packages":[],"prev":{"headline":"crypto: essiv - Check ssize for decryption and in-place encryption","id":"CVE-2025-40019"},"products":["Linux"],"published":"2025-10-24","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 shift-out-of-bounds error in the Linux kernel peak_usb CAN driver can cause a denial of service.","url":"https://insights.sbomify.com/CVE-2025-40020/"}