<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 05:39:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93135 — bpf: Reject programs with inlined helpers if JIT is not available</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93135</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject programs with inlined helpers if JIT is not available&lt;/p&gt;
&lt;p&gt;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-&amp;gt;imm) in bpf_do_misc_fixups(). This is because the
helper is expected to be inlined by the JIT compiler later. Therefore,
insn-&amp;gt;imm remains as the raw helper enum ID.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;When the interpreter executes (__bpf_call_base + insn-&amp;gt;imm) with the
unpatched raw ID, it jumps into an invalid address space, triggering
an instruction alignment fault or a kernel panic.&lt;/p&gt;
&lt;p&gt;Although these helpers have valid C implementations in the kernel, the
omission of offset rewriting makes runtime interpreter fallback fatal.&lt;/p&gt;
&lt;p&gt;Fix this by setting &amp;#39;prog-&amp;gt;jit_required = 1&amp;#39; 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject programs with inlined helpers if JIT is not available&lt;/p&gt;
&lt;p&gt;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-&amp;gt;imm) in bpf_do_misc_fixups(). This is because the
helper is expected to be inlined by the JIT compiler later. Therefore,
insn-&amp;gt;imm remains as the raw helper enum ID.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;When the interpreter executes (__bpf_call_base + insn-&amp;gt;imm) with the
unpatched raw ID, it jumps into an invalid address space, triggering
an instruction alignment fault or a kernel panic.&lt;/p&gt;
&lt;p&gt;Although these helpers have valid C implementations in the kernel, the
omission of offset rewriting makes runtime interpreter fallback fatal.&lt;/p&gt;
&lt;p&gt;Fix this by setting &amp;#39;prog-&amp;gt;jit_required = 1&amp;#39; 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93135</guid>
    </item>
  </channel>
</rss>
