<?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://db.gcve.eu</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, 20 Oct 2026 14:23:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-14370</title>
      <link>https://db.gcve.eu/vuln/bdu:2025-14370</link>
      <description>bdu:2025-14370</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2025-14370</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47317</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2021-47317</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/bpf: Fix detecting BPF atomic instructions&lt;/p&gt;
&lt;p&gt;Commit 91c960b0056672 (&amp;#34;bpf: Rename BPF_XADD and prepare to encode other
atomics in .imm&amp;#34;) converted BPF_XADD to BPF_ATOMIC and added a way to
distinguish instructions based on the immediate field. Existing JIT
implementations were updated to check for the immediate field and to
reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH)
in the immediate field.&lt;/p&gt;
&lt;p&gt;However, the check added to powerpc64 JIT did not look at the correct
BPF instruction. Due to this, such programs would be accepted and
incorrectly JIT&amp;#39;ed resulting in soft lockups, as seen with the atomic
bounds test. Fix this by looking at the correct immediate value.&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;powerpc/bpf: Fix detecting BPF atomic instructions&lt;/p&gt;
&lt;p&gt;Commit 91c960b0056672 (&amp;#34;bpf: Rename BPF_XADD and prepare to encode other
atomics in .imm&amp;#34;) converted BPF_XADD to BPF_ATOMIC and added a way to
distinguish instructions based on the immediate field. Existing JIT
implementations were updated to check for the immediate field and to
reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH)
in the immediate field.&lt;/p&gt;
&lt;p&gt;However, the check added to powerpc64 JIT did not look at the correct
BPF instruction. Due to this, such programs would be accepted and
incorrectly JIT&amp;#39;ed resulting in soft lockups, as seen with the atomic
bounds test. Fix this by looking at the correct immediate value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2021-47317</guid>
    </item>
    <item>
      <title>GHSA-2p2c-qgqr-9ghc</title>
      <link>https://db.gcve.eu/vuln/ghsa-2p2c-qgqr-9ghc</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;powerpc/bpf: Fix detecting BPF atomic instructions&lt;/p&gt;
&lt;p&gt;Commit 91c960b0056672 (&amp;#34;bpf: Rename BPF_XADD and prepare to encode other
atomics in .imm&amp;#34;) converted BPF_XADD to BPF_ATOMIC and added a way to
distinguish instructions based on the immediate field. Existing JIT
implementations were updated to check for the immediate field and to
reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH)
in the immediate field.&lt;/p&gt;
&lt;p&gt;However, the check added to powerpc64 JIT did not look at the correct
BPF instruction. Due to this, such programs would be accepted and
incorrectly JIT&amp;#39;ed resulting in soft lockups, as seen with the atomic
bounds test. Fix this by looking at the correct immediate value.&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;powerpc/bpf: Fix detecting BPF atomic instructions&lt;/p&gt;
&lt;p&gt;Commit 91c960b0056672 (&amp;#34;bpf: Rename BPF_XADD and prepare to encode other
atomics in .imm&amp;#34;) converted BPF_XADD to BPF_ATOMIC and added a way to
distinguish instructions based on the immediate field. Existing JIT
implementations were updated to check for the immediate field and to
reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH)
in the immediate field.&lt;/p&gt;
&lt;p&gt;However, the check added to powerpc64 JIT did not look at the correct
BPF instruction. Due to this, such programs would be accepted and
incorrectly JIT&amp;#39;ed resulting in soft lockups, as seen with the atomic
bounds test. Fix this by looking at the correct immediate value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2p2c-qgqr-9ghc</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47317</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2021-47317</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: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 (&amp;#34;bpf: Rename BPF_XADD and prepare to encode other atomics in .imm&amp;#34;) converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT&amp;#39;ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value.&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: powerpc/bpf: Fix detecting BPF atomic instructions Commit 91c960b0056672 (&amp;#34;bpf: Rename BPF_XADD and prepare to encode other atomics in .imm&amp;#34;) converted BPF_XADD to BPF_ATOMIC and added a way to distinguish instructions based on the immediate field. Existing JIT implementations were updated to check for the immediate field and to reject programs utilizing anything more than BPF_ADD (such as BPF_FETCH) in the immediate field. However, the check added to powerpc64 JIT did not look at the correct BPF instruction. Due to this, such programs would be accepted and incorrectly JIT&amp;#39;ed resulting in soft lockups, as seen with the atomic bounds test. Fix this by looking at the correct immediate value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2021-47317</guid>
    </item>
  </channel>
</rss>
