<?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>Thu, 08 Oct 2026 09:40:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21853 — bpf: avoid holding freeze_mutex during mmap operation</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-21853</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: avoid holding freeze_mutex during mmap operation&lt;/p&gt;
&lt;p&gt;We use map-&amp;gt;freeze_mutex to prevent races between map_freeze() and
memory mapping BPF map contents with writable permissions. The way we
naively do this means we&amp;#39;ll hold freeze_mutex for entire duration of all
the mm and VMA manipulations, which is completely unnecessary. This can
potentially also lead to deadlocks, as reported by syzbot in [0].&lt;/p&gt;
&lt;p&gt;So, instead, hold freeze_mutex only during writeability checks, bump
(proactively) &amp;#34;write active&amp;#34; count for the map, unlock the mutex and
proceed with mmap logic. And only if something went wrong during mmap
logic, then undo that &amp;#34;write active&amp;#34; counter increment.&lt;/p&gt;
&lt;p&gt;[0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: avoid holding freeze_mutex during mmap operation&lt;/p&gt;
&lt;p&gt;We use map-&amp;gt;freeze_mutex to prevent races between map_freeze() and
memory mapping BPF map contents with writable permissions. The way we
naively do this means we&amp;#39;ll hold freeze_mutex for entire duration of all
the mm and VMA manipulations, which is completely unnecessary. This can
potentially also lead to deadlocks, as reported by syzbot in [0].&lt;/p&gt;
&lt;p&gt;So, instead, hold freeze_mutex only during writeability checks, bump
(proactively) &amp;#34;write active&amp;#34; count for the map, unlock the mutex and
proceed with mmap logic. And only if something went wrong during mmap
logic, then undo that &amp;#34;write active&amp;#34; counter increment.&lt;/p&gt;
&lt;p&gt;[0] https://lore.kernel.org/bpf/678dcbc9.050a0220.303755.0066.GAE@google.com/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-21853</guid>
    </item>
  </channel>
</rss>
