{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40078 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40078 is a missing authorization vulnerability in Linux, published on 28 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-40078 and fix it if it is affected.\n\nWhat it is: CVE-2025-40078 is a missing authorization vulnerability in Linux, published on 28 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-40078 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-40078/ (Markdown: https://insights.sbomify.com/CVE-2025-40078/index.md)","id":"CVE-2025-40078","markdown":"https://insights.sbomify.com/CVE-2025-40078/index.md","name":"CVE-2025-40078","record":{"aliases":["AZL-68840","BELL-CVE-2025-40078","DEBIAN-CVE-2025-40078","GHSA-rvq5-xw4g-6wj7","ROOT-OS-DEBIAN-11-CVE-2025-40078","ROOT-OS-DEBIAN-12-CVE-2025-40078","ROOT-OS-DEBIAN-13-CVE-2025-40078","ROOT-OS-UBUNTU-2204-CVE-2025-40078","ROOT-OS-UBUNTU-2404-CVE-2025-40078","UBUNTU-CVE-2025-40078"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel BPF","requires_auth":"low_privilege","summary":"A missing validation check in the Linux kernel BPF subsystem allows local attackers to trigger a verifier bug and kernel warning, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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\nbpf: Explicitly check accesses to bpf_sock_addr\n\nSyzkaller found a kernel warning on the following sock_addr program:\n\n    0: r0 = 0\n    1: r2 = *(u32 *)(r1 +60)\n    2: exit\n\nwhich triggers:\n\n    verifier bug: error during ctx access conversion (0)\n\nThis is happening because offset 60 in bpf_sock_addr corresponds to an\nimplicit padding of 4 bytes, right after msg_src_ip4. Access to this\npadding isn't rejected in sock_addr_is_valid_access and it thus later\nfails to convert the access.\n\nThis patch fixes it by explicitly checking the various fields of\nbpf_sock_addr in sock_addr_is_valid_access.\n\nI checked the other ctx structures and is_valid_access functions and\ndidn't find any other similar cases. Other cases of (properly handled)\npadding are covered in new tests in a subsequent patch.","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":"bpf: Explicitly check accesses to bpf_sock_addr","id":"CVE-2025-40078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"riscv, bpf: Sign extend struct ops return values properly","id":"CVE-2025-40079"},"packages":[],"prev":{"headline":"f2fs: fix to avoid overflow while left shift operation","id":"CVE-2025-40077"},"products":["Linux"],"published":"2025-10-28","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-15","vendors":["Linux"]},"summary":"A missing validation check in the Linux kernel BPF subsystem allows local attackers to trigger a verifier bug and kernel warning, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-40078/"}