<?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 03:31:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43055 — scsi: target: file: Use kzalloc_flex for aio_cmd</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43055</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;scsi: target: file: Use kzalloc_flex for aio_cmd&lt;/p&gt;
&lt;p&gt;The target_core_file doesn&amp;#39;t initialize the aio_cmd-&amp;gt;iocb for the
ki_write_stream. When a write command fd_execute_rw_aio() is executed,
we may get a bogus ki_write_stream value, causing unintended write
failure status when checking iocb-&amp;gt;ki_write_stream &amp;gt; max_write_streams
in the block device.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s just use kzalloc_flex when allocating the aio_cmd and let
ki_write_stream=0 to fix this issue.&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;scsi: target: file: Use kzalloc_flex for aio_cmd&lt;/p&gt;
&lt;p&gt;The target_core_file doesn&amp;#39;t initialize the aio_cmd-&amp;gt;iocb for the
ki_write_stream. When a write command fd_execute_rw_aio() is executed,
we may get a bogus ki_write_stream value, causing unintended write
failure status when checking iocb-&amp;gt;ki_write_stream &amp;gt; max_write_streams
in the block device.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s just use kzalloc_flex when allocating the aio_cmd and let
ki_write_stream=0 to fix this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43055</guid>
    </item>
  </channel>
</rss>
