<?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://vulnerability.circl.lu</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>Sun, 04 Oct 2026 07:19:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38451 — md/md-bitmap: fix GPF in bitmap_get_stats()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38451</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;md/md-bitmap: fix GPF in bitmap_get_stats()&lt;/p&gt;
&lt;p&gt;The commit message of commit 6ec1f0239485 (&amp;#34;md/md-bitmap: fix stats
collection for external bitmaps&amp;#34;) states:&lt;/p&gt;
&lt;p&gt;Remove the external bitmap check as the statistics should be
    available regardless of bitmap storage location.&lt;/p&gt;
&lt;p&gt;Return -EINVAL only for invalid bitmap with no storage (neither in
    superblock nor in external file).&lt;/p&gt;
&lt;p&gt;But, the code does not adhere to the above, as it does only check for
a valid super-block for &amp;#34;internal&amp;#34; bitmaps. Hence, we observe:&lt;/p&gt;
&lt;p&gt;Oops: GPF, probably for non-canonical address 0x1cd66f1f40000028
RIP: 0010:bitmap_get_stats+0x45/0xd0
Call Trace:&lt;/p&gt;
&lt;p&gt;seq_read_iter+0x2b9/0x46a
 seq_read+0x12f/0x180
 proc_reg_read+0x57/0xb0
 vfs_read+0xf6/0x380
 ksys_read+0x6d/0xf0
 do_syscall_64+0x8c/0x1b0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;We fix this by checking the existence of a super-block for both the
internal and external case.&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;md/md-bitmap: fix GPF in bitmap_get_stats()&lt;/p&gt;
&lt;p&gt;The commit message of commit 6ec1f0239485 (&amp;#34;md/md-bitmap: fix stats
collection for external bitmaps&amp;#34;) states:&lt;/p&gt;
&lt;p&gt;Remove the external bitmap check as the statistics should be
    available regardless of bitmap storage location.&lt;/p&gt;
&lt;p&gt;Return -EINVAL only for invalid bitmap with no storage (neither in
    superblock nor in external file).&lt;/p&gt;
&lt;p&gt;But, the code does not adhere to the above, as it does only check for
a valid super-block for &amp;#34;internal&amp;#34; bitmaps. Hence, we observe:&lt;/p&gt;
&lt;p&gt;Oops: GPF, probably for non-canonical address 0x1cd66f1f40000028
RIP: 0010:bitmap_get_stats+0x45/0xd0
Call Trace:&lt;/p&gt;
&lt;p&gt;seq_read_iter+0x2b9/0x46a
 seq_read+0x12f/0x180
 proc_reg_read+0x57/0xb0
 vfs_read+0xf6/0x380
 ksys_read+0x6d/0xf0
 do_syscall_64+0x8c/0x1b0
 entry_SYSCALL_64_after_hwframe+0x76/0x7e&lt;/p&gt;
&lt;p&gt;We fix this by checking the existence of a super-block for both the
internal and external case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38451</guid>
    </item>
  </channel>
</rss>
