<?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:41:30 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72154</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-72154</guid>
    </item>
    <item>
      <title>EUVD-2026-353958</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353958</link>
      <description>EUVD-2026-353958</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353958</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72154</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72154</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;openrisc: Fix jump_label smp syncing&lt;/p&gt;
&lt;p&gt;The original commit 8c30b0018f9d (&amp;#34;openrisc: Add jump label support&amp;#34;)
copies from arm64 and does not properly consider how icache invalidation
on remote cores works in OpenRISC.  On OpenRISC remote icaches need to
be invalidated otherwise static key&amp;#39;s may remain state after updating.&lt;/p&gt;
&lt;p&gt;Fix SMP cache syncing by:&lt;/p&gt;
&lt;p&gt;1. Properly invalidate remote core icaches on SMP systems by using
    icache_all_inv.  The old code uses kick_all_cpus_sync() which runs a
    no-op IPI function call on remote CPU&amp;#39;s which does execute a lot of
    code and flushes many cache lines in the process, but does not flush
    all and it&amp;#39;s not correct on OpenRISC.
 2. For architectures that do not have WRITETHROUGH caches be sure
    to flush the dcache after patching.&lt;/p&gt;
&lt;p&gt;To test this I first reproduced the issue using a custom test module
[0].  The test confirmed that some icache lines maintained stale
static_key code sequences after calling static_branch_enable().  After
this patch there are no longer jump_label coherency issues.&lt;/p&gt;
&lt;p&gt;[0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test&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;openrisc: Fix jump_label smp syncing&lt;/p&gt;
&lt;p&gt;The original commit 8c30b0018f9d (&amp;#34;openrisc: Add jump label support&amp;#34;)
copies from arm64 and does not properly consider how icache invalidation
on remote cores works in OpenRISC.  On OpenRISC remote icaches need to
be invalidated otherwise static key&amp;#39;s may remain state after updating.&lt;/p&gt;
&lt;p&gt;Fix SMP cache syncing by:&lt;/p&gt;
&lt;p&gt;1. Properly invalidate remote core icaches on SMP systems by using
    icache_all_inv.  The old code uses kick_all_cpus_sync() which runs a
    no-op IPI function call on remote CPU&amp;#39;s which does execute a lot of
    code and flushes many cache lines in the process, but does not flush
    all and it&amp;#39;s not correct on OpenRISC.
 2. For architectures that do not have WRITETHROUGH caches be sure
    to flush the dcache after patching.&lt;/p&gt;
&lt;p&gt;To test this I first reproduced the issue using a custom test module
[0].  The test confirmed that some icache lines maintained stale
static_key code sequences after calling static_branch_enable().  After
this patch there are no longer jump_label coherency issues.&lt;/p&gt;
&lt;p&gt;[0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72154</guid>
    </item>
    <item>
      <title>GHSA-w2g7-86j7-x792</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w2g7-86j7-x792</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;openrisc: Fix jump_label smp syncing&lt;/p&gt;
&lt;p&gt;The original commit 8c30b0018f9d (&amp;#34;openrisc: Add jump label support&amp;#34;)
copies from arm64 and does not properly consider how icache invalidation
on remote cores works in OpenRISC.  On OpenRISC remote icaches need to
be invalidated otherwise static key&amp;#39;s may remain state after updating.&lt;/p&gt;
&lt;p&gt;Fix SMP cache syncing by:&lt;/p&gt;
&lt;p&gt;1. Properly invalidate remote core icaches on SMP systems by using
    icache_all_inv.  The old code uses kick_all_cpus_sync() which runs a
    no-op IPI function call on remote CPU&amp;#39;s which does execute a lot of
    code and flushes many cache lines in the process, but does not flush
    all and it&amp;#39;s not correct on OpenRISC.
 2. For architectures that do not have WRITETHROUGH caches be sure
    to flush the dcache after patching.&lt;/p&gt;
&lt;p&gt;To test this I first reproduced the issue using a custom test module
[0].  The test confirmed that some icache lines maintained stale
static_key code sequences after calling static_branch_enable().  After
this patch there are no longer jump_label coherency issues.&lt;/p&gt;
&lt;p&gt;[0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test&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;openrisc: Fix jump_label smp syncing&lt;/p&gt;
&lt;p&gt;The original commit 8c30b0018f9d (&amp;#34;openrisc: Add jump label support&amp;#34;)
copies from arm64 and does not properly consider how icache invalidation
on remote cores works in OpenRISC.  On OpenRISC remote icaches need to
be invalidated otherwise static key&amp;#39;s may remain state after updating.&lt;/p&gt;
&lt;p&gt;Fix SMP cache syncing by:&lt;/p&gt;
&lt;p&gt;1. Properly invalidate remote core icaches on SMP systems by using
    icache_all_inv.  The old code uses kick_all_cpus_sync() which runs a
    no-op IPI function call on remote CPU&amp;#39;s which does execute a lot of
    code and flushes many cache lines in the process, but does not flush
    all and it&amp;#39;s not correct on OpenRISC.
 2. For architectures that do not have WRITETHROUGH caches be sure
    to flush the dcache after patching.&lt;/p&gt;
&lt;p&gt;To test this I first reproduced the issue using a custom test module
[0].  The test confirmed that some icache lines maintained stale
static_key code sequences after calling static_branch_enable().  After
this patch there are no longer jump_label coherency issues.&lt;/p&gt;
&lt;p&gt;[0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w2g7-86j7-x792</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72154</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72154</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 115 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: openrisc: Fix jump_label smp syncing The original commit 8c30b0018f9d (&amp;#34;openrisc: Add jump label support&amp;#34;) copies from arm64 and does not properly consider how icache invalidation on remote cores works in OpenRISC.  On OpenRISC remote icaches need to be invalidated otherwise static key&amp;#39;s may remain state after updating. Fix SMP cache syncing by:  1. Properly invalidate remote core icaches on SMP systems by using     icache_all_inv.  The old code uses kick_all_cpus_sync() which runs a     no-op IPI function call on remote CPU&amp;#39;s which does execute a lot of     code and flushes many cache lines in the process, but does not flush     all and it&amp;#39;s not correct on OpenRISC.  2. For architectures that do not have WRITETHROUGH caches be sure     to flush the dcache after patching. To test this I first reproduced the issue using a custom test module [0].  The test confirmed that some icache lines maintained stale static_key code sequences after calling static_branch_enable().  After this patch there are no longer jump_label coherency issues. [0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test&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 115 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: openrisc: Fix jump_label smp syncing The original commit 8c30b0018f9d (&amp;#34;openrisc: Add jump label support&amp;#34;) copies from arm64 and does not properly consider how icache invalidation on remote cores works in OpenRISC.  On OpenRISC remote icaches need to be invalidated otherwise static key&amp;#39;s may remain state after updating. Fix SMP cache syncing by:  1. Properly invalidate remote core icaches on SMP systems by using     icache_all_inv.  The old code uses kick_all_cpus_sync() which runs a     no-op IPI function call on remote CPU&amp;#39;s which does execute a lot of     code and flushes many cache lines in the process, but does not flush     all and it&amp;#39;s not correct on OpenRISC.  2. For architectures that do not have WRITETHROUGH caches be sure     to flush the dcache after patching. To test this I first reproduced the issue using a custom test module [0].  The test confirmed that some icache lines maintained stale static_key code sequences after calling static_branch_enable().  After this patch there are no longer jump_label coherency issues. [0] https://github.com/stffrdhrn/or1k-utils/tree/master/tests/smp_static_key_test&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72154</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
