{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93135 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93135 is a denial of service 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-93135 and fix it if it is affected.\n\nWhat it is: CVE-2026-93135 is a denial of service 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-93135 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-93135/ (Markdown: https://insights.sbomify.com/CVE-2026-93135/index.md)","id":"CVE-2026-93135","markdown":"https://insights.sbomify.com/CVE-2026-93135/index.md","name":"CVE-2026-93135","record":{"aliases":["BELL-CVE-2026-93135","DEBIAN-CVE-2026-93135","GHSA-6hpp-rhfj-hgrp","UBUNTU-CVE-2026-93135"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel panic by loading BPF programs with inlined helpers when JIT is disabled or fails, requiring low privileges.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: Reject programs with inlined helpers if JIT is not available\n\nWhen an architecture (such as LoongArch, ARM64, and RISC-V) implements\nbpf_jit_inlines_helper_call(), the verifier skips rewriting the helper\ncall offset (insn-\u003eimm) in bpf_do_misc_fixups(). This is because the\nhelper is expected to be inlined by the JIT compiler later. Therefore,\ninsn-\u003eimm remains as the raw helper enum ID.\n\nHowever, if JIT is disabled at runtime (net.core.bpf_jit_enable=0) or\nif JIT compilation fails dynamically (e.g., due to OOM), the program\nfalls back to the BPF interpreter.\n\nWhen the interpreter executes (__bpf_call_base + insn-\u003eimm) with the\nunpatched raw ID, it jumps into an invalid address space, triggering\nan instruction alignment fault or a kernel panic.\n\nAlthough these helpers have valid C implementations in the kernel, the\nomission of offset rewriting makes runtime interpreter fallback fatal.\n\nFix this by setting 'prog-\u003ejit_required = 1' when helper call rewriting\nis skipped for JIT inlining. This ensures that such programs are safely\nrejected if JIT is not available, preventing the runtime kernel panic.","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 programs with inlined helpers if JIT is not available","id":"CVE-2026-93135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation","id":"CVE-2026-93136"},"packages":[],"prev":{"headline":"printk: Fix possible console use-after-free","id":"CVE-2026-93134"},"products":["Linux"],"published":"2026-09-17","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-19","vendors":["Linux"]},"summary":"A local attacker can cause a kernel panic by loading BPF programs with inlined helpers when JIT is disabled or fails, requiring low privileges.","url":"https://insights.sbomify.com/CVE-2026-93135/"}