<?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>Mon, 12 Oct 2026 20:32:39 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-12291</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-12291</link>
      <description>bdu:2026-12291</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-12291</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23275</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23275</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-23275</guid>
    </item>
    <item>
      <title>EUVD-2026-347628</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347628</link>
      <description>EUVD-2026-347628</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347628</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23275</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23275</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation&lt;/p&gt;
&lt;p&gt;If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while
the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of
IORING_SQ_TASKRUN to happen in the small window of swapping into the
new rings and the old rings being freed.&lt;/p&gt;
&lt;p&gt;Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is
protected by RCU. The task work flags manipulation is inside RCU
already, and if the resize ring freeing is done post an RCU synchronize,
then there&amp;#39;s no need to add locking to the fast path of task work
additions.&lt;/p&gt;
&lt;p&gt;Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode
that supports ring resizing. If this ever changes, then they too need to
use the io_ctx_mark_taskrun() helper.&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;io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation&lt;/p&gt;
&lt;p&gt;If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while
the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of
IORING_SQ_TASKRUN to happen in the small window of swapping into the
new rings and the old rings being freed.&lt;/p&gt;
&lt;p&gt;Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is
protected by RCU. The task work flags manipulation is inside RCU
already, and if the resize ring freeing is done post an RCU synchronize,
then there&amp;#39;s no need to add locking to the fast path of task work
additions.&lt;/p&gt;
&lt;p&gt;Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode
that supports ring resizing. If this ever changes, then they too need to
use the io_ctx_mark_taskrun() helper.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23275</guid>
    </item>
    <item>
      <title>GHSA-w9fp-2248-jh3m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w9fp-2248-jh3m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation&lt;/p&gt;
&lt;p&gt;If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while
the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of
IORING_SQ_TASKRUN to happen in the small window of swapping into the
new rings and the old rings being freed.&lt;/p&gt;
&lt;p&gt;Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is
protected by RCU. The task work flags manipulation is inside RCU
already, and if the resize ring freeing is done post an RCU synchronize,
then there&amp;#39;s no need to add locking to the fast path of task work
additions.&lt;/p&gt;
&lt;p&gt;Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode
that supports ring resizing. If this ever changes, then they too need to
use the io_ctx_mark_taskrun() helper.&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;io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation&lt;/p&gt;
&lt;p&gt;If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while
the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of
IORING_SQ_TASKRUN to happen in the small window of swapping into the
new rings and the old rings being freed.&lt;/p&gt;
&lt;p&gt;Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is
protected by RCU. The task work flags manipulation is inside RCU
already, and if the resize ring freeing is done post an RCU synchronize,
then there&amp;#39;s no need to add locking to the fast path of task work
additions.&lt;/p&gt;
&lt;p&gt;Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode
that supports ring resizing. If this ever changes, then they too need to
use the io_ctx_mark_taskrun() helper.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w9fp-2248-jh3m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23275</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23275</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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of IORING_SQ_TASKRUN to happen in the small window of swapping into the new rings and the old rings being freed. Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is protected by RCU. The task work flags manipulation is inside RCU already, and if the resize ring freeing is done post an RCU synchronize, then there&amp;#39;s no need to add locking to the fast path of task work additions. Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode that supports ring resizing. If this ever changes, then they too need to use the io_ctx_mark_taskrun() helper.&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 106 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring: ensure ctx-&amp;gt;rings is stable for task work flags manipulation If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while the ring is being resized, it&amp;#39;s possible for the OR&amp;#39;ing of IORING_SQ_TASKRUN to happen in the small window of swapping into the new rings and the old rings being freed. Prevent this by adding a 2nd -&amp;gt;rings pointer, -&amp;gt;rings_rcu, which is protected by RCU. The task work flags manipulation is inside RCU already, and if the resize ring freeing is done post an RCU synchronize, then there&amp;#39;s no need to add locking to the fast path of task work additions. Note: this is only done for DEFER_TASKRUN, as that&amp;#39;s the only setup mode that supports ring resizing. If this ever changes, then they too need to use the io_ctx_mark_taskrun() helper.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23275</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0809 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0809</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, zur Manipulation und Offenlegung von Daten oder zu einer Speicherbeschädigung führen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, zur Manipulation und Offenlegung von Daten oder zu einer Speicherbeschädigung führen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0809</guid>
    </item>
  </channel>
</rss>
