{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93125 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93125 is a high-severity vulnerability in Linux, published on 17 Sep 2026. 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-2026-93125 and fix it if it is affected.\n\nWhat it is: CVE-2026-93125 is a high-severity vulnerability in Linux, published on 17 Sep 2026. 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-2026-93125 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-2026-93125/ (Markdown: https://insights.sbomify.com/CVE-2026-93125/index.md)","id":"CVE-2026-93125","markdown":"https://insights.sbomify.com/CVE-2026-93125/index.md","name":"CVE-2026-93125","record":{"aliases":["AZL-101876","BELL-CVE-2026-93125","DEBIAN-CVE-2026-93125","GHSA-vqq3-2x9h-9pmg","UBUNTU-CVE-2026-93125"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel BPF","requires_auth":"low_privilege","summary":"A missing bounds check in the Linux kernel BPF verifier allows integer truncation, potentially leading to memory corruption and privilege escalation.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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 rdonly/rdwr_buf_size kfunc arguments that exceed u32 max\n\ncheck_kfunc_args() detects a kfunc argument named rdonly_buf_size or\nrdwr_buf_size and stores reg-\u003evar_off.value into meta-\u003er0_size, a u64,\nand does not bound it. check_kfunc_call() later copies that value into\nthe returned register's mem_size field:\n\n  meta-\u003er0_size = reg-\u003evar_off.value;\n  ...\n  regs[BPF_REG_0].mem_size = meta.r0_size;\n\nregs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set\ngets truncated instead of causing a load-time rejection, so the verifier\nrecords a PTR_TO_MEM register with an approximately 4 GiB mem_size for\nwhatever allocation the kfunc returned. A later access check against\nthat register uses the truncated, wrong bound.\n\nReject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the\npoint meta-\u003er0_size is set.","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 rdonly/rdwr_buf_size kfunc arguments that exceed u32 max","id":"CVE-2026-93125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"remoteproc: qcom_q6v5_adsp: Fix reference leak for device node","id":"CVE-2026-93126"},"packages":[],"prev":{"headline":"platform/x86: asus-wireless: Fail probe when there is no ACPI match","id":"CVE-2026-93124"},"products":["Linux"],"published":"2026-09-17","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A missing bounds check in the Linux kernel BPF verifier allows integer truncation, potentially leading to memory corruption and privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-93125/"}