VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

CVE-2026-93135: Linux kernel · bpf: Reject programs with inlined helpers if JIT is not available

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to f1c27922576edccb99d0257827d09bd05c0304a6 or 21c6445366795fa3a89954e1d318e7c8afdef843 when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f1c27922576edccb99d0257827d09bd05c0304a6, 21c6445366795fa3a89954e1d318e7c8afdef843

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to f1c27922576edccb99d0257827d09bd05c0304a6 or 21c6445366795fa3a89954e1d318e7c8afdef843.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 2ddec2c80b4402c293c7e6e0881cecaaf77e8cec, < f1c27922576edccb99d0257827d09bd05c0304a6	Fixed in f1c27922576edccb99d0257827d09bd05c0304a6
LinuxLinux	Affected ≥ 2ddec2c80b4402c293c7e6e0881cecaaf77e8cec, < 21c6445366795fa3a89954e1d318e7c8afdef843	Fixed in 21c6445366795fa3a89954e1d318e7c8afdef843
LinuxLinux	Affected =6.10	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Reject programs with inlined helpers if JIT is not available When an architecture (such as LoongArch, ARM64, and RISC-V) implements bpf_jit_inlines_helper_call(), the verifier skips rewriting the helper call offset (insn->imm) in bpf_do_misc_fixups(). This is because the helper is expected to be inlined by the JIT compiler later. Therefore, insn->imm remains as the raw helper enum ID. However, if JIT is disabled at runtime (net.core.bpf_jit_enable=0) or if JIT compilation fails dynamically (e.g., due to OOM), the program falls back to the BPF interpreter. When the interpreter executes (__bpf_call_base + insn->imm) with the unpatched raw ID, it jumps into an invalid address space, triggering an instruction alignment fault or a kernel panic. Although these helpers have valid C implementations in the kernel, the omission of offset rewriting makes runtime interpreter fallback fatal. Fix this by setting 'prog->jit_required = 1' when helper call rewriting is skipped for JIT inlining. This ensures that such programs are safely rejected if JIT is not available, preventing the runtime kernel panic.

References

Community reviews

Loading reviews…