<?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:21:59 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-05990</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-05990</link>
      <description>bdu:2026-05990</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-05990</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53172</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-53172</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-2023-53172</guid>
    </item>
    <item>
      <title>EUVD-2026-311881</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311881</link>
      <description>EUVD-2026-311881</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311881</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53172</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-53172</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds&lt;/p&gt;
&lt;p&gt;Commit 56124d6c87fd (&amp;#34;fsverity: support enabling with tree block size &amp;lt;
PAGE_SIZE&amp;#34;) changed FS_IOC_ENABLE_VERITY to use __kernel_read() to read
the file&amp;#39;s data, instead of direct pagecache accesses.&lt;/p&gt;
&lt;p&gt;An unintended consequence of this is that the
&amp;#39;WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_READ))&amp;#39; in __kernel_read() became
reachable by fuzz tests.  This happens if FS_IOC_ENABLE_VERITY is called
on a fd opened with access mode 3, which means &amp;#34;ioctl access only&amp;#34;.&lt;/p&gt;
&lt;p&gt;Arguably, FS_IOC_ENABLE_VERITY should work on ioctl-only fds.  But
ioctl-only fds are a weird Linux extension that is rarely used and that
few people even know about.  (The documentation for FS_IOC_ENABLE_VERITY
even specifically says it requires O_RDONLY.)  It&amp;#39;s probably not
worthwhile to make the ioctl internally open a new fd just to handle
this case.  Thus, just reject the ioctl on such fds for now.&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;fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds&lt;/p&gt;
&lt;p&gt;Commit 56124d6c87fd (&amp;#34;fsverity: support enabling with tree block size &amp;lt;
PAGE_SIZE&amp;#34;) changed FS_IOC_ENABLE_VERITY to use __kernel_read() to read
the file&amp;#39;s data, instead of direct pagecache accesses.&lt;/p&gt;
&lt;p&gt;An unintended consequence of this is that the
&amp;#39;WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_READ))&amp;#39; in __kernel_read() became
reachable by fuzz tests.  This happens if FS_IOC_ENABLE_VERITY is called
on a fd opened with access mode 3, which means &amp;#34;ioctl access only&amp;#34;.&lt;/p&gt;
&lt;p&gt;Arguably, FS_IOC_ENABLE_VERITY should work on ioctl-only fds.  But
ioctl-only fds are a weird Linux extension that is rarely used and that
few people even know about.  (The documentation for FS_IOC_ENABLE_VERITY
even specifically says it requires O_RDONLY.)  It&amp;#39;s probably not
worthwhile to make the ioctl internally open a new fd just to handle
this case.  Thus, just reject the ioctl on such fds for now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-53172</guid>
    </item>
    <item>
      <title>GHSA-f2h8-669r-j5fx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f2h8-669r-j5fx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds&lt;/p&gt;
&lt;p&gt;Commit 56124d6c87fd (&amp;#34;fsverity: support enabling with tree block size &amp;lt;
PAGE_SIZE&amp;#34;) changed FS_IOC_ENABLE_VERITY to use __kernel_read() to read
the file&amp;#39;s data, instead of direct pagecache accesses.&lt;/p&gt;
&lt;p&gt;An unintended consequence of this is that the
&amp;#39;WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_READ))&amp;#39; in __kernel_read() became
reachable by fuzz tests.  This happens if FS_IOC_ENABLE_VERITY is called
on a fd opened with access mode 3, which means &amp;#34;ioctl access only&amp;#34;.&lt;/p&gt;
&lt;p&gt;Arguably, FS_IOC_ENABLE_VERITY should work on ioctl-only fds.  But
ioctl-only fds are a weird Linux extension that is rarely used and that
few people even know about.  (The documentation for FS_IOC_ENABLE_VERITY
even specifically says it requires O_RDONLY.)  It&amp;#39;s probably not
worthwhile to make the ioctl internally open a new fd just to handle
this case.  Thus, just reject the ioctl on such fds for now.&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;fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds&lt;/p&gt;
&lt;p&gt;Commit 56124d6c87fd (&amp;#34;fsverity: support enabling with tree block size &amp;lt;
PAGE_SIZE&amp;#34;) changed FS_IOC_ENABLE_VERITY to use __kernel_read() to read
the file&amp;#39;s data, instead of direct pagecache accesses.&lt;/p&gt;
&lt;p&gt;An unintended consequence of this is that the
&amp;#39;WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_READ))&amp;#39; in __kernel_read() became
reachable by fuzz tests.  This happens if FS_IOC_ENABLE_VERITY is called
on a fd opened with access mode 3, which means &amp;#34;ioctl access only&amp;#34;.&lt;/p&gt;
&lt;p&gt;Arguably, FS_IOC_ENABLE_VERITY should work on ioctl-only fds.  But
ioctl-only fds are a weird Linux extension that is rarely used and that
few people even know about.  (The documentation for FS_IOC_ENABLE_VERITY
even specifically says it requires O_RDONLY.)  It&amp;#39;s probably not
worthwhile to make the ioctl internally open a new fd just to handle
this case.  Thus, just reject the ioctl on such fds for now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f2h8-669r-j5fx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53172</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53172</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds Commit 56124d6c87fd (&amp;#34;fsverity: support enabling with tree block size &amp;lt; PAGE_SIZE&amp;#34;) changed FS_IOC_ENABLE_VERITY to use __kernel_read() to read the file&amp;#39;s data, instead of direct pagecache accesses. An unintended consequence of this is that the &amp;#39;WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_READ))&amp;#39; in __kernel_read() became reachable by fuzz tests.  This happens if FS_IOC_ENABLE_VERITY is called on a fd opened with access mode 3, which means &amp;#34;ioctl access only&amp;#34;. Arguably, FS_IOC_ENABLE_VERITY should work on ioctl-only fds.  But ioctl-only fds are a weird Linux extension that is rarely used and that few people even know about.  (The documentation for FS_IOC_ENABLE_VERITY even specifically says it requires O_RDONLY.)  It&amp;#39;s probably not worthwhile to make the ioctl internally open a new fd just to handle this case.  Thus, just reject the ioctl on such fds for now.&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds Commit 56124d6c87fd (&amp;#34;fsverity: support enabling with tree block size &amp;lt; PAGE_SIZE&amp;#34;) changed FS_IOC_ENABLE_VERITY to use __kernel_read() to read the file&amp;#39;s data, instead of direct pagecache accesses. An unintended consequence of this is that the &amp;#39;WARN_ON_ONCE(!(file-&amp;gt;f_mode &amp;amp; FMODE_READ))&amp;#39; in __kernel_read() became reachable by fuzz tests.  This happens if FS_IOC_ENABLE_VERITY is called on a fd opened with access mode 3, which means &amp;#34;ioctl access only&amp;#34;. Arguably, FS_IOC_ENABLE_VERITY should work on ioctl-only fds.  But ioctl-only fds are a weird Linux extension that is rarely used and that few people even know about.  (The documentation for FS_IOC_ENABLE_VERITY even specifically says it requires O_RDONLY.)  It&amp;#39;s probably not worthwhile to make the ioctl internally open a new fd just to handle this case.  Thus, just reject the ioctl on such fds for now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53172</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2053 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2053</guid>
    </item>
  </channel>
</rss>
