<?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 11:27:12 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-72190 — CVE-2026-72190 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72190</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-72190</guid>
    </item>
    <item>
      <title>EUVD-2026-353693</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353693</link>
      <description>EUVD-2026-353693</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353693</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72190</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72190</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs: fix mrec_lock ABBA deadlock in rename&lt;/p&gt;
&lt;p&gt;ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an
inode&amp;#39;s mrec_lock before taking the mrec_lock of its parent directory.&lt;/p&gt;
&lt;p&gt;ntfs_rename() takes old_ni-&amp;gt;mrec_lock and old_dir_ni-&amp;gt;mrec_lock
before taking new_ni-&amp;gt;mrec_lock for an existing target, or
new_dir_ni-&amp;gt;mrec_lock for a cross-directory rename.
This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds
the target inode, or when ntfs_dir_fsync() holds a child target
directory, while rename() holds the parent directory and waits for the
target.&lt;/p&gt;
&lt;p&gt;Fix this by locking the existing target inode before taking any parent
directory mrec_lock. For cross-directory renames where the target parent
is a descendant of the source parent, lock the target parent before the
source parent so the directory order matches the child-to-parent order used
by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().&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;ntfs: fix mrec_lock ABBA deadlock in rename&lt;/p&gt;
&lt;p&gt;ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an
inode&amp;#39;s mrec_lock before taking the mrec_lock of its parent directory.&lt;/p&gt;
&lt;p&gt;ntfs_rename() takes old_ni-&amp;gt;mrec_lock and old_dir_ni-&amp;gt;mrec_lock
before taking new_ni-&amp;gt;mrec_lock for an existing target, or
new_dir_ni-&amp;gt;mrec_lock for a cross-directory rename.
This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds
the target inode, or when ntfs_dir_fsync() holds a child target
directory, while rename() holds the parent directory and waits for the
target.&lt;/p&gt;
&lt;p&gt;Fix this by locking the existing target inode before taking any parent
directory mrec_lock. For cross-directory renames where the target parent
is a descendant of the source parent, lock the target parent before the
source parent so the directory order matches the child-to-parent order used
by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72190</guid>
    </item>
    <item>
      <title>GHSA-7xmj-mqhm-5492</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7xmj-mqhm-5492</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs: fix mrec_lock ABBA deadlock in rename&lt;/p&gt;
&lt;p&gt;ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an
inode&amp;#39;s mrec_lock before taking the mrec_lock of its parent directory.&lt;/p&gt;
&lt;p&gt;ntfs_rename() takes old_ni-&amp;gt;mrec_lock and old_dir_ni-&amp;gt;mrec_lock
before taking new_ni-&amp;gt;mrec_lock for an existing target, or
new_dir_ni-&amp;gt;mrec_lock for a cross-directory rename.
This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds
the target inode, or when ntfs_dir_fsync() holds a child target
directory, while rename() holds the parent directory and waits for the
target.&lt;/p&gt;
&lt;p&gt;Fix this by locking the existing target inode before taking any parent
directory mrec_lock. For cross-directory renames where the target parent
is a descendant of the source parent, lock the target parent before the
source parent so the directory order matches the child-to-parent order used
by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().&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;ntfs: fix mrec_lock ABBA deadlock in rename&lt;/p&gt;
&lt;p&gt;ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an
inode&amp;#39;s mrec_lock before taking the mrec_lock of its parent directory.&lt;/p&gt;
&lt;p&gt;ntfs_rename() takes old_ni-&amp;gt;mrec_lock and old_dir_ni-&amp;gt;mrec_lock
before taking new_ni-&amp;gt;mrec_lock for an existing target, or
new_dir_ni-&amp;gt;mrec_lock for a cross-directory rename.
This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds
the target inode, or when ntfs_dir_fsync() holds a child target
directory, while rename() holds the parent directory and waits for the
target.&lt;/p&gt;
&lt;p&gt;Fix this by locking the existing target inode before taking any parent
directory mrec_lock. For cross-directory renames where the target parent
is a descendant of the source parent, lock the target parent before the
source parent so the directory order matches the child-to-parent order used
by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7xmj-mqhm-5492</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72190</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72190</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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ntfs: fix mrec_lock ABBA deadlock in rename ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an inode&amp;#39;s mrec_lock before taking the mrec_lock of its parent directory. ntfs_rename() takes old_ni-&amp;gt;mrec_lock and old_dir_ni-&amp;gt;mrec_lock before taking new_ni-&amp;gt;mrec_lock for an existing target, or new_dir_ni-&amp;gt;mrec_lock for a cross-directory rename. This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds the target inode, or when ntfs_dir_fsync() holds a child target directory, while rename() holds the parent directory and waits for the target. Fix this by locking the existing target inode before taking any parent directory mrec_lock. For cross-directory renames where the target parent is a descendant of the source parent, lock the target parent before the source parent so the directory order matches the child-to-parent order used by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().&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 93 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ntfs: fix mrec_lock ABBA deadlock in rename ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an inode&amp;#39;s mrec_lock before taking the mrec_lock of its parent directory. ntfs_rename() takes old_ni-&amp;gt;mrec_lock and old_dir_ni-&amp;gt;mrec_lock before taking new_ni-&amp;gt;mrec_lock for an existing target, or new_dir_ni-&amp;gt;mrec_lock for a cross-directory rename. This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds the target inode, or when ntfs_dir_fsync() holds a child target directory, while rename() holds the parent directory and waits for the target. Fix this by locking the existing target inode before taking any parent directory mrec_lock. For cross-directory renames where the target parent is a descendant of the source parent, lock the target parent before the source parent so the directory order matches the child-to-parent order used by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72190</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>
