{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40169 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40169 is a high-severity 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-40169 and fix it if it is affected.\n\nWhat it is: CVE-2025-40169 is a high-severity 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-40169 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-40169/ (Markdown: https://insights.sbomify.com/CVE-2025-40169/index.md)","id":"CVE-2025-40169","markdown":"https://insights.sbomify.com/CVE-2025-40169/index.md","name":"CVE-2025-40169","record":{"aliases":["BELL-CVE-2025-40169","DEBIAN-CVE-2025-40169","GHSA-pfch-hqrr-v4q4","ROOT-OS-UBUNTU-2404-CVE-2025-40169","UBUNTU-CVE-2025-40169"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel BPF","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel BPF verifier allowed negative offsets in ALU operations, potentially enabling malicious BPF programs to bypass validation and execute arbitrary code.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject negative offsets for ALU ops\n\nWhen verifying BPF programs, the check_alu_op() function validates\ninstructions with ALU operations. The 'offset' field in these\ninstructions is a signed 16-bit integer.\n\nThe existing check 'insn-\u003eoff \u003e 1' was intended to ensure the offset is\neither 0, or 1 for BPF_MOD/BPF_DIV. However, because 'insn-\u003eoff' is\nsigned, this check incorrectly accepts all negative values (e.g., -1).\n\nThis commit tightens the validation by changing the condition to\n'(insn-\u003eoff != 0 \u0026\u0026 insn-\u003eoff != 1)'. This ensures that any value\nother than the explicitly permitted 0 and 1 is rejected, hardening the\nverifier against malformed BPF programs.","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: Reject negative offsets for ALU ops","id":"CVE-2025-40169","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"net: use dst_dev_rcu() in sk_setup_caps()","id":"CVE-2025-40170"},"packages":[],"prev":{"headline":"smc: Use __sk_dst_get() and dst_dev_rcu() in smc_clc_prfx_match().","id":"CVE-2025-40168"},"products":["Linux"],"published":"2025-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A flaw in the Linux kernel BPF verifier allowed negative offsets in ALU operations, potentially enabling malicious BPF programs to bypass validation and execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2025-40169/"}