<?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 01:39:32 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-80804 — CVE-2026-80804 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80804</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80804</guid>
    </item>
    <item>
      <title>EUVD-2026-363822</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-363822</link>
      <description>EUVD-2026-363822</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-363822</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80804</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80804</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: restore nofs context unconditionally in xfs_trans_roll&lt;/p&gt;
&lt;p&gt;When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
is cleared but only restored in the success path.  This leaves the
error path without nofs protection, causing a circular lock dependency
between xfs_nondir_ilock_class and fs_reclaim:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;xfs_nondir_ilock_class);
                               lock(fs_reclaim);
                               lock(&amp;amp;xfs_nondir_ilock_class);
  lock(fs_reclaim);&lt;/p&gt;
&lt;p&gt;Fix this by moving xfs_trans_set_context() before the error check so
that nofs context is always restored on the new transaction.&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;xfs: restore nofs context unconditionally in xfs_trans_roll&lt;/p&gt;
&lt;p&gt;When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
is cleared but only restored in the success path.  This leaves the
error path without nofs protection, causing a circular lock dependency
between xfs_nondir_ilock_class and fs_reclaim:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;xfs_nondir_ilock_class);
                               lock(fs_reclaim);
                               lock(&amp;amp;xfs_nondir_ilock_class);
  lock(fs_reclaim);&lt;/p&gt;
&lt;p&gt;Fix this by moving xfs_trans_set_context() before the error check so
that nofs context is always restored on the new transaction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80804</guid>
    </item>
    <item>
      <title>GHSA-m2xq-p36j-8h55</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m2xq-p36j-8h55</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xfs: restore nofs context unconditionally in xfs_trans_roll&lt;/p&gt;
&lt;p&gt;When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
is cleared but only restored in the success path.  This leaves the
error path without nofs protection, causing a circular lock dependency
between xfs_nondir_ilock_class and fs_reclaim:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;xfs_nondir_ilock_class);
                               lock(fs_reclaim);
                               lock(&amp;amp;xfs_nondir_ilock_class);
  lock(fs_reclaim);&lt;/p&gt;
&lt;p&gt;Fix this by moving xfs_trans_set_context() before the error check so
that nofs context is always restored on the new transaction.&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;xfs: restore nofs context unconditionally in xfs_trans_roll&lt;/p&gt;
&lt;p&gt;When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context
is cleared but only restored in the success path.  This leaves the
error path without nofs protection, causing a circular lock dependency
between xfs_nondir_ilock_class and fs_reclaim:&lt;/p&gt;
&lt;p&gt;CPU0                    CPU1
       ----                    ----
  lock(&amp;amp;xfs_nondir_ilock_class);
                               lock(fs_reclaim);
                               lock(&amp;amp;xfs_nondir_ilock_class);
  lock(fs_reclaim);&lt;/p&gt;
&lt;p&gt;Fix this by moving xfs_trans_set_context() before the error check so
that nofs context is always restored on the new transaction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m2xq-p36j-8h55</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11773-1 — kernel-devel-7.2.5-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.5-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11773-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80804</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80804</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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: restore nofs context unconditionally in xfs_trans_roll When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context is cleared but only restored in the success path.  This leaves the error path without nofs protection, causing a circular lock dependency between xfs_nondir_ilock_class and fs_reclaim:        CPU0                    CPU1        ----                    ----   lock(&amp;amp;xfs_nondir_ilock_class);                                lock(fs_reclaim);                                lock(&amp;amp;xfs_nondir_ilock_class);   lock(fs_reclaim); Fix this by moving xfs_trans_set_context() before the error check so that nofs context is always restored on the new transaction.&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 117 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xfs: restore nofs context unconditionally in xfs_trans_roll When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context is cleared but only restored in the success path.  This leaves the error path without nofs protection, causing a circular lock dependency between xfs_nondir_ilock_class and fs_reclaim:        CPU0                    CPU1        ----                    ----   lock(&amp;amp;xfs_nondir_ilock_class);                                lock(fs_reclaim);                                lock(&amp;amp;xfs_nondir_ilock_class);   lock(fs_reclaim); Fix this by moving xfs_trans_set_context() before the error check so that nofs context is always restored on the new transaction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80804</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3211 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Speicherfehler und Kernel-Abstürze beziehungsweise Denial-of-Service-Zustände auszulösen, Speicher außerhalb vorgesehener Grenzen auszulesen sowie in einzelnen Fällen weitere Sicherheitsauswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3211</guid>
    </item>
  </channel>
</rss>
