<?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>Thu, 01 Oct 2026 16:06:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68348 — block: fix memory leak in __blkdev_issue_zero_pages</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68348</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;block: fix memory leak in __blkdev_issue_zero_pages&lt;/p&gt;
&lt;p&gt;Move the fatal signal check before bio_alloc() to prevent a memory
leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.&lt;/p&gt;
&lt;p&gt;Previously, the bio was allocated before checking for a fatal signal.
If a signal was pending, the code would break out of the loop without
freeing or chaining the just-allocated bio, causing a memory leak.&lt;/p&gt;
&lt;p&gt;This matches the pattern already used in __blkdev_issue_write_zeroes()
where the signal check precedes the allocation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;block: fix memory leak in __blkdev_issue_zero_pages&lt;/p&gt;
&lt;p&gt;Move the fatal signal check before bio_alloc() to prevent a memory
leak when BLKDEV_ZERO_KILLABLE is set and a fatal signal is pending.&lt;/p&gt;
&lt;p&gt;Previously, the bio was allocated before checking for a fatal signal.
If a signal was pending, the code would break out of the loop without
freeing or chaining the just-allocated bio, causing a memory leak.&lt;/p&gt;
&lt;p&gt;This matches the pattern already used in __blkdev_issue_write_zeroes()
where the signal check precedes the allocation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68348</guid>
    </item>
  </channel>
</rss>
