{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93112 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93112 is a high-severity memory corruption 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-93112 and fix it if it is affected.\n\nWhat it is: CVE-2026-93112 is a high-severity memory corruption 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-93112 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-93112/ (Markdown: https://insights.sbomify.com/CVE-2026-93112/index.md)","id":"CVE-2026-93112","markdown":"https://insights.sbomify.com/CVE-2026-93112/index.md","name":"CVE-2026-93112","record":{"aliases":["BELL-CVE-2026-93112","DEBIAN-CVE-2026-93112","GHSA-8wvc-jp6j-85p4","UBUNTU-CVE-2026-93112"],"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 type confusion in the Linux kernel BPF subsystem allows writing to read-only memory, potentially enabling privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Require a BPF cpumask for bpf_cpumask_populate()\n\nbpf_cpumask_populate() writes to its destination with bitmap_copy(), but\nthe destination is typed as struct cpumask *. That allows the verifier to\naccept borrowed cpumask pointers returned by read-only kfuncs, such as\nscx_bpf_get_online_cpumask(), as a writable destination.\n\nMake the destination a struct bpf_cpumask * so populate follows the same\nownership rule as the other mutating cpumask kfuncs. Query kfuncs continue\nto accept const struct cpumask * inputs.","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: Require a BPF cpumask for bpf_cpumask_populate()","id":"CVE-2026-93112","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"clk: qcom: camcc-sc8280xp: unregister CAMCC_GDSC_CLK","id":"CVE-2026-93113"},"packages":[],"prev":{"headline":"bpf: Mark tracing_multi trampolines as ftrace managed","id":"CVE-2026-93111"},"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-19","vendors":["Linux"]},"summary":"A type confusion in the Linux kernel BPF subsystem allows writing to read-only memory, potentially enabling privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-93112/"}