<?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>Tue, 29 Sep 2026 09:33:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-45026 — s390/dasd: fix error recovery leading to data corruption on ESE devices</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-45026</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;s390/dasd: fix error recovery leading to data corruption on ESE devices&lt;/p&gt;
&lt;p&gt;Extent Space Efficient (ESE) or thin provisioned volumes need to be
formatted on demand during usual IO processing.&lt;/p&gt;
&lt;p&gt;The dasd_ese_needs_format function checks for error codes that signal
the non existence of a proper track format.&lt;/p&gt;
&lt;p&gt;The check for incorrect length is to imprecise since other error cases
leading to transport of insufficient data also have this flag set.
This might lead to data corruption in certain error cases for example
during a storage server warmstart.&lt;/p&gt;
&lt;p&gt;Fix by removing the check for incorrect length and replacing by
explicitly checking for invalid track format in transport mode.&lt;/p&gt;
&lt;p&gt;Also remove the check for file protected since this is not a valid
ESE handling case.&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;s390/dasd: fix error recovery leading to data corruption on ESE devices&lt;/p&gt;
&lt;p&gt;Extent Space Efficient (ESE) or thin provisioned volumes need to be
formatted on demand during usual IO processing.&lt;/p&gt;
&lt;p&gt;The dasd_ese_needs_format function checks for error codes that signal
the non existence of a proper track format.&lt;/p&gt;
&lt;p&gt;The check for incorrect length is to imprecise since other error cases
leading to transport of insufficient data also have this flag set.
This might lead to data corruption in certain error cases for example
during a storage server warmstart.&lt;/p&gt;
&lt;p&gt;Fix by removing the check for incorrect length and replacing by
explicitly checking for invalid track format in transport mode.&lt;/p&gt;
&lt;p&gt;Also remove the check for file protected since this is not a valid
ESE handling case.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-45026</guid>
    </item>
  </channel>
</rss>
