<?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:09:02 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01774</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01774</link>
      <description>bdu:2025-01774</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01774</guid>
    </item>
    <item>
      <title>fkie_cve-2024-57937</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-57937</link>
      <description>&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-57937</guid>
    </item>
    <item>
      <title>GHSA-cjf9-gqj4-56m7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cjf9-gqj4-56m7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: reinstate ability to map write-sealed memfd mappings read-only&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm: reinstate ability to map write-sealed memfd mappings
read-only&amp;#34;.&lt;/p&gt;
&lt;p&gt;In commit 158978945f31 (&amp;#34;mm: perform the mapping_map_writable() check
after call_mmap()&amp;#34;) (and preceding changes in the same series) it became
possible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.&lt;/p&gt;
&lt;p&gt;Commit 5de195060b2e (&amp;#34;mm: resolve faulty mmap_region() error path
behaviour&amp;#34;) unintentionally undid this logic by moving the
mapping_map_writable() check before the shmem_mmap() hook is invoked,
thereby regressing this change.&lt;/p&gt;
&lt;p&gt;This series reworks how we both permit write-sealed mappings being mapped
read-only and disallow mprotect() from undoing the write-seal, fixing this
regression.&lt;/p&gt;
&lt;p&gt;We also add a regression test to ensure that we do not accidentally
regress this in future.&lt;/p&gt;
&lt;p&gt;Thanks to Julian Orth for reporting this regression.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;In commit 158978945f31 (&amp;#34;mm: perform the mapping_map_writable() check
after call_mmap()&amp;#34;) (and preceding changes in the same series) it became
possible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.&lt;/p&gt;
&lt;p&gt;This was previously unnecessarily disallowed, despite the man page
documentation indicating that it would be, thereby limiting the usefulness
of F_SEAL_WRITE logic.&lt;/p&gt;
&lt;p&gt;We fixed this by adapting logic that existed for the F_SEAL_FUTURE_WRITE
seal (one which disallows future writes to the memfd) to also b…&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;mm: reinstate ability to map write-sealed memfd mappings read-only&lt;/p&gt;
&lt;p&gt;Patch series &amp;#34;mm: reinstate ability to map write-sealed memfd mappings
read-only&amp;#34;.&lt;/p&gt;
&lt;p&gt;In commit 158978945f31 (&amp;#34;mm: perform the mapping_map_writable() check
after call_mmap()&amp;#34;) (and preceding changes in the same series) it became
possible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.&lt;/p&gt;
&lt;p&gt;Commit 5de195060b2e (&amp;#34;mm: resolve faulty mmap_region() error path
behaviour&amp;#34;) unintentionally undid this logic by moving the
mapping_map_writable() check before the shmem_mmap() hook is invoked,
thereby regressing this change.&lt;/p&gt;
&lt;p&gt;This series reworks how we both permit write-sealed mappings being mapped
read-only and disallow mprotect() from undoing the write-seal, fixing this
regression.&lt;/p&gt;
&lt;p&gt;We also add a regression test to ensure that we do not accidentally
regress this in future.&lt;/p&gt;
&lt;p&gt;Thanks to Julian Orth for reporting this regression.&lt;/p&gt;
&lt;p&gt;This patch (of 2):&lt;/p&gt;
&lt;p&gt;In commit 158978945f31 (&amp;#34;mm: perform the mapping_map_writable() check
after call_mmap()&amp;#34;) (and preceding changes in the same series) it became
possible to mmap() F_SEAL_WRITE sealed memfd mappings read-only.&lt;/p&gt;
&lt;p&gt;This was previously unnecessarily disallowed, despite the man page
documentation indicating that it would be, thereby limiting the usefulness
of F_SEAL_WRITE logic.&lt;/p&gt;
&lt;p&gt;We fixed this by adapting logic that existed for the F_SEAL_FUTURE_WRITE
seal (one which disallows future writes to the memfd) to also b…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cjf9-gqj4-56m7</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57937</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57937</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 69 more&lt;/p&gt;
&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&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 69 more&lt;/p&gt;
&lt;p&gt;Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57937</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0155 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0155</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um 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 und um nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0155</guid>
    </item>
  </channel>
</rss>
