<?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://cve.radiocsirt.org</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>Fri, 02 Oct 2026 19:38:13 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89581</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-89581</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-89581</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>EUVD-2026-367301</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367301</link>
      <description>EUVD-2026-367301</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367301</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89581</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-89581</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, x86: Fix per-CPU address resolution into an extended register&lt;/p&gt;
&lt;p&gt;The destination of the per-CPU address MOV is encoded in ModRM.reg,
which is extended by REX.R, but the REX prefix is built with
add_1mod(), which sets REX.B. REX.B extends ModRM.rm and SIB.base, and
this instruction addresses memory as disp32 with no base, so the bit
has no effect at all and the high register bit is simply lost.&lt;/p&gt;
&lt;p&gt;Every is_ereg() destination therefore resolves to the wrong register,
picking whichever one shares the low three bits:&lt;/p&gt;
&lt;p&gt;R5 -&amp;gt; RAX    R7 -&amp;gt; RBP    R8 -&amp;gt; RSI    R9 -&amp;gt; RDI&lt;/p&gt;
&lt;p&gt;With BPF_REG_5, whose reg2hex is 0, the emitted&lt;/p&gt;
&lt;p&gt;65 49 03 04 25 &amp;lt;off&amp;gt;	add %gs:&amp;lt;off&amp;gt;,%rax&lt;/p&gt;
&lt;p&gt;adds the per-CPU offset to RAX rather than R8. The destination keeps
the unadjusted address and RAX is clobbered, so the program goes on to
dereference a pointer that was never made per-CPU:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000607e386a8894
  RIP: bpf_prog_707837aafd2aa9ae_update_percpu_data+0x93/0xc9
  Call Trace:
   __bpf_prog_test_run_raw_tp+0x2dc/0x7d0
   __flush_smp_call_function_queue+0x1e9/0xc80
  Kernel panic - not syncing: Fatal exception in interrupt&lt;/p&gt;
&lt;p&gt;R5 is the mildest of the four, aliasing a scratch register and faulting
at the store. R7 aliases RBP and would corrupt the frame pointer, R8
and R9 alias the argument registers.&lt;/p&gt;
&lt;p&gt;Use add_2mod() so the register goes through REX.R, matching how
add_2reg() places it in ModRM.reg and ho…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, x86: Fix per-CPU address resolution into an extended register&lt;/p&gt;
&lt;p&gt;The destination of the per-CPU address MOV is encoded in ModRM.reg,
which is extended by REX.R, but the REX prefix is built with
add_1mod(), which sets REX.B. REX.B extends ModRM.rm and SIB.base, and
this instruction addresses memory as disp32 with no base, so the bit
has no effect at all and the high register bit is simply lost.&lt;/p&gt;
&lt;p&gt;Every is_ereg() destination therefore resolves to the wrong register,
picking whichever one shares the low three bits:&lt;/p&gt;
&lt;p&gt;R5 -&amp;gt; RAX    R7 -&amp;gt; RBP    R8 -&amp;gt; RSI    R9 -&amp;gt; RDI&lt;/p&gt;
&lt;p&gt;With BPF_REG_5, whose reg2hex is 0, the emitted&lt;/p&gt;
&lt;p&gt;65 49 03 04 25 &amp;lt;off&amp;gt;	add %gs:&amp;lt;off&amp;gt;,%rax&lt;/p&gt;
&lt;p&gt;adds the per-CPU offset to RAX rather than R8. The destination keeps
the unadjusted address and RAX is clobbered, so the program goes on to
dereference a pointer that was never made per-CPU:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000607e386a8894
  RIP: bpf_prog_707837aafd2aa9ae_update_percpu_data+0x93/0xc9
  Call Trace:
   __bpf_prog_test_run_raw_tp+0x2dc/0x7d0
   __flush_smp_call_function_queue+0x1e9/0xc80
  Kernel panic - not syncing: Fatal exception in interrupt&lt;/p&gt;
&lt;p&gt;R5 is the mildest of the four, aliasing a scratch register and faulting
at the store. R7 aliases RBP and would corrupt the frame pointer, R8
and R9 alias the argument registers.&lt;/p&gt;
&lt;p&gt;Use add_2mod() so the register goes through REX.R, matching how
add_2reg() places it in ModRM.reg and ho…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-89581</guid>
    </item>
    <item>
      <title>GHSA-vx2x-82ww-5r7r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vx2x-82ww-5r7r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, x86: Fix per-CPU address resolution into an extended register&lt;/p&gt;
&lt;p&gt;The destination of the per-CPU address MOV is encoded in ModRM.reg,
which is extended by REX.R, but the REX prefix is built with
add_1mod(), which sets REX.B. REX.B extends ModRM.rm and SIB.base, and
this instruction addresses memory as disp32 with no base, so the bit
has no effect at all and the high register bit is simply lost.&lt;/p&gt;
&lt;p&gt;Every is_ereg() destination therefore resolves to the wrong register,
picking whichever one shares the low three bits:&lt;/p&gt;
&lt;p&gt;R5 -&amp;gt; RAX    R7 -&amp;gt; RBP    R8 -&amp;gt; RSI    R9 -&amp;gt; RDI&lt;/p&gt;
&lt;p&gt;With BPF_REG_5, whose reg2hex is 0, the emitted&lt;/p&gt;
&lt;p&gt;65 49 03 04 25 &amp;lt;off&amp;gt;	add %gs:&amp;lt;off&amp;gt;,%rax&lt;/p&gt;
&lt;p&gt;adds the per-CPU offset to RAX rather than R8. The destination keeps
the unadjusted address and RAX is clobbered, so the program goes on to
dereference a pointer that was never made per-CPU:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000607e386a8894
  RIP: bpf_prog_707837aafd2aa9ae_update_percpu_data+0x93/0xc9
  Call Trace:
   __bpf_prog_test_run_raw_tp+0x2dc/0x7d0
   __flush_smp_call_function_queue+0x1e9/0xc80
  Kernel panic - not syncing: Fatal exception in interrupt&lt;/p&gt;
&lt;p&gt;R5 is the mildest of the four, aliasing a scratch register and faulting
at the store. R7 aliases RBP and would corrupt the frame pointer, R8
and R9 alias the argument registers.&lt;/p&gt;
&lt;p&gt;Use add_2mod() so the register goes through REX.R, matching how
add_2reg() places it in ModRM.reg and ho…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, x86: Fix per-CPU address resolution into an extended register&lt;/p&gt;
&lt;p&gt;The destination of the per-CPU address MOV is encoded in ModRM.reg,
which is extended by REX.R, but the REX prefix is built with
add_1mod(), which sets REX.B. REX.B extends ModRM.rm and SIB.base, and
this instruction addresses memory as disp32 with no base, so the bit
has no effect at all and the high register bit is simply lost.&lt;/p&gt;
&lt;p&gt;Every is_ereg() destination therefore resolves to the wrong register,
picking whichever one shares the low three bits:&lt;/p&gt;
&lt;p&gt;R5 -&amp;gt; RAX    R7 -&amp;gt; RBP    R8 -&amp;gt; RSI    R9 -&amp;gt; RDI&lt;/p&gt;
&lt;p&gt;With BPF_REG_5, whose reg2hex is 0, the emitted&lt;/p&gt;
&lt;p&gt;65 49 03 04 25 &amp;lt;off&amp;gt;	add %gs:&amp;lt;off&amp;gt;,%rax&lt;/p&gt;
&lt;p&gt;adds the per-CPU offset to RAX rather than R8. The destination keeps
the unadjusted address and RAX is clobbered, so the program goes on to
dereference a pointer that was never made per-CPU:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000607e386a8894
  RIP: bpf_prog_707837aafd2aa9ae_update_percpu_data+0x93/0xc9
  Call Trace:
   __bpf_prog_test_run_raw_tp+0x2dc/0x7d0
   __flush_smp_call_function_queue+0x1e9/0xc80
  Kernel panic - not syncing: Fatal exception in interrupt&lt;/p&gt;
&lt;p&gt;R5 is the mildest of the four, aliasing a scratch register and faulting
at the store. R7 aliases RBP and would corrupt the frame pointer, R8
and R9 alias the argument registers.&lt;/p&gt;
&lt;p&gt;Use add_2mod() so the register goes through REX.R, matching how
add_2reg() places it in ModRM.reg and ho…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vx2x-82ww-5r7r</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89581</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89581</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, x86: Fix per-CPU address resolution into an extended register The destination of the per-CPU address MOV is encoded in ModRM.reg, which is extended by REX.R, but the REX prefix is built with add_1mod(), which sets REX.B. REX.B extends ModRM.rm and SIB.base, and this instruction addresses memory as disp32 with no base, so the bit has no effect at all and the high register bit is simply lost. Every is_ereg() destination therefore resolves to the wrong register, picking whichever one shares the low three bits:   R5 -&amp;gt; RAX    R7 -&amp;gt; RBP    R8 -&amp;gt; RSI    R9 -&amp;gt; RDI With BPF_REG_5, whose reg2hex is 0, the emitted   65 49 03 04 25 &amp;lt;off&amp;gt;	add %gs:&amp;lt;off&amp;gt;,%rax adds the per-CPU offset to RAX rather than R8. The destination keeps the unadjusted address and RAX is clobbered, so the program goes on to dereference a pointer that was never made per-CPU:   BUG: unable to handle page fault for address: 0000607e386a8894   RIP: bpf_prog_707837aafd2aa9ae_update_percpu_data+0x93/0xc9   Call Trace:    __bpf_prog_test_run_raw_tp+0x2dc/0x7d0    __flush_smp_call_function_queue+0x1e9/0xc80   Kernel panic - not syncing: Fatal exception in interrupt R5 is the mildest of the four, aliasing a scratch register and faulting at the store. R7 aliases RBP and would corrupt the frame pointer, R8 and R9 alias the argument registers. Use add_2mod() so the register goes through REX.R, matching how add_2reg() places it in ModRM.reg and how emit_pri…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, x86: Fix per-CPU address resolution into an extended register The destination of the per-CPU address MOV is encoded in ModRM.reg, which is extended by REX.R, but the REX prefix is built with add_1mod(), which sets REX.B. REX.B extends ModRM.rm and SIB.base, and this instruction addresses memory as disp32 with no base, so the bit has no effect at all and the high register bit is simply lost. Every is_ereg() destination therefore resolves to the wrong register, picking whichever one shares the low three bits:   R5 -&amp;gt; RAX    R7 -&amp;gt; RBP    R8 -&amp;gt; RSI    R9 -&amp;gt; RDI With BPF_REG_5, whose reg2hex is 0, the emitted   65 49 03 04 25 &amp;lt;off&amp;gt;	add %gs:&amp;lt;off&amp;gt;,%rax adds the per-CPU offset to RAX rather than R8. The destination keeps the unadjusted address and RAX is clobbered, so the program goes on to dereference a pointer that was never made per-CPU:   BUG: unable to handle page fault for address: 0000607e386a8894   RIP: bpf_prog_707837aafd2aa9ae_update_percpu_data+0x93/0xc9   Call Trace:    __bpf_prog_test_run_raw_tp+0x2dc/0x7d0    __flush_smp_call_function_queue+0x1e9/0xc80   Kernel panic - not syncing: Fatal exception in interrupt R5 is the mildest of the four, aliasing a scratch register and faulting at the store. R7 aliases RBP and would corrupt the frame pointer, R8 and R9 alias the argument registers. Use add_2mod() so the register goes through REX.R, matching how add_2reg() places it in ModRM.reg and how emit_pri…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-89581</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
