<?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>Sat, 03 Oct 2026 12:31:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-11584</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-11584</link>
      <description>bdu:2024-11584</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-11584</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0578 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578</link>
      <description>certfr-2024-avi-0578</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578</guid>
    </item>
    <item>
      <title>EUVD-2026-309840</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309840</link>
      <description>EUVD-2026-309840</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309840</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47607</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47607</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix kernel address leakage in atomic cmpxchg&amp;#39;s r0 aux reg&lt;/p&gt;
&lt;p&gt;The implementation of BPF_CMPXCHG on a high level has the following parameters:&lt;/p&gt;
&lt;p&gt;.-[old-val]                                          .-[new-val]
  BPF_R0 = cmpxchg{32,64}(DST_REG + insn-&amp;gt;off, BPF_R0, SRC_REG)
                          `-[mem-loc]          `-[old-val]&lt;/p&gt;
&lt;p&gt;Given a BPF insn can only have two registers (dst, src), the R0 is fixed and
used as an auxilliary register for input (old value) as well as output (returning
old value from memory location). While the verifier performs a number of safety
checks, it misses to reject unprivileged programs where R0 contains a pointer as
old value.&lt;/p&gt;
&lt;p&gt;Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer
with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the
guessed address into the map slot as a scalar, and using the map value pointer as
R0 while SRC_REG has a canary value to detect a matching address.&lt;/p&gt;
&lt;p&gt;Fix it by checking R0 for pointers, and reject if that&amp;#39;s the case for unprivileged
programs.&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: Fix kernel address leakage in atomic cmpxchg&amp;#39;s r0 aux reg&lt;/p&gt;
&lt;p&gt;The implementation of BPF_CMPXCHG on a high level has the following parameters:&lt;/p&gt;
&lt;p&gt;.-[old-val]                                          .-[new-val]
  BPF_R0 = cmpxchg{32,64}(DST_REG + insn-&amp;gt;off, BPF_R0, SRC_REG)
                          `-[mem-loc]          `-[old-val]&lt;/p&gt;
&lt;p&gt;Given a BPF insn can only have two registers (dst, src), the R0 is fixed and
used as an auxilliary register for input (old value) as well as output (returning
old value from memory location). While the verifier performs a number of safety
checks, it misses to reject unprivileged programs where R0 contains a pointer as
old value.&lt;/p&gt;
&lt;p&gt;Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer
with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the
guessed address into the map slot as a scalar, and using the map value pointer as
R0 while SRC_REG has a canary value to detect a matching address.&lt;/p&gt;
&lt;p&gt;Fix it by checking R0 for pointers, and reject if that&amp;#39;s the case for unprivileged
programs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47607</guid>
    </item>
    <item>
      <title>GHSA-fp67-w4xm-4hj6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fp67-w4xm-4hj6</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix kernel address leakage in atomic cmpxchg&amp;#39;s r0 aux reg&lt;/p&gt;
&lt;p&gt;The implementation of BPF_CMPXCHG on a high level has the following parameters:&lt;/p&gt;
&lt;p&gt;.-[old-val]                                          .-[new-val]
  BPF_R0 = cmpxchg{32,64}(DST_REG + insn-&amp;gt;off, BPF_R0, SRC_REG)
                          `-[mem-loc]          `-[old-val]&lt;/p&gt;
&lt;p&gt;Given a BPF insn can only have two registers (dst, src), the R0 is fixed and
used as an auxilliary register for input (old value) as well as output (returning
old value from memory location). While the verifier performs a number of safety
checks, it misses to reject unprivileged programs where R0 contains a pointer as
old value.&lt;/p&gt;
&lt;p&gt;Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer
with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the
guessed address into the map slot as a scalar, and using the map value pointer as
R0 while SRC_REG has a canary value to detect a matching address.&lt;/p&gt;
&lt;p&gt;Fix it by checking R0 for pointers, and reject if that&amp;#39;s the case for unprivileged
programs.&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: Fix kernel address leakage in atomic cmpxchg&amp;#39;s r0 aux reg&lt;/p&gt;
&lt;p&gt;The implementation of BPF_CMPXCHG on a high level has the following parameters:&lt;/p&gt;
&lt;p&gt;.-[old-val]                                          .-[new-val]
  BPF_R0 = cmpxchg{32,64}(DST_REG + insn-&amp;gt;off, BPF_R0, SRC_REG)
                          `-[mem-loc]          `-[old-val]&lt;/p&gt;
&lt;p&gt;Given a BPF insn can only have two registers (dst, src), the R0 is fixed and
used as an auxilliary register for input (old value) as well as output (returning
old value from memory location). While the verifier performs a number of safety
checks, it misses to reject unprivileged programs where R0 contains a pointer as
old value.&lt;/p&gt;
&lt;p&gt;Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer
with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the
guessed address into the map slot as a scalar, and using the map value pointer as
R0 while SRC_REG has a canary value to detect a matching address.&lt;/p&gt;
&lt;p&gt;Fix it by checking R0 for pointers, and reject if that&amp;#39;s the case for unprivileged
programs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fp67-w4xm-4hj6</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2372-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2372-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:2372-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47607</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47607</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix kernel address leakage in atomic cmpxchg&amp;#39;s r0 aux reg The implementation of BPF_CMPXCHG on a high level has the following parameters:   .-[old-val]                                          .-[new-val]   BPF_R0 = cmpxchg{32,64}(DST_REG + insn-&amp;gt;off, BPF_R0, SRC_REG)                           `-[mem-loc]          `-[old-val] Given a BPF insn can only have two registers (dst, src), the R0 is fixed and used as an auxilliary register for input (old value) as well as output (returning old value from memory location). While the verifier performs a number of safety checks, it misses to reject unprivileged programs where R0 contains a pointer as old value. Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the guessed address into the map slot as a scalar, and using the map value pointer as R0 while SRC_REG has a canary value to detect a matching address. Fix it by checking R0 for pointers, and reject if that&amp;#39;s the case for unprivileged programs.&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf: Fix kernel address leakage in atomic cmpxchg&amp;#39;s r0 aux reg The implementation of BPF_CMPXCHG on a high level has the following parameters:   .-[old-val]                                          .-[new-val]   BPF_R0 = cmpxchg{32,64}(DST_REG + insn-&amp;gt;off, BPF_R0, SRC_REG)                           `-[mem-loc]          `-[old-val] Given a BPF insn can only have two registers (dst, src), the R0 is fixed and used as an auxilliary register for input (old value) as well as output (returning old value from memory location). While the verifier performs a number of safety checks, it misses to reject unprivileged programs where R0 contains a pointer as old value. Through brute-forcing it takes about ~16sec on my machine to leak a kernel pointer with BPF_CMPXCHG. The PoC is basically probing for kernel addresses by storing the guessed address into the map slot as a scalar, and using the map value pointer as R0 while SRC_REG has a canary value to detect a matching address. Fix it by checking R0 for pointers, and reject if that&amp;#39;s the case for unprivileged programs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47607</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1418 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</guid>
    </item>
  </channel>
</rss>
