<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T03:31:48.572777+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-43055</id>
    <title>CVE-2026-43055 — scsi: target: file: Use kzalloc_flex for aio_cmd</title>
    <updated>2026-09-29T03:31:48.575524+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: target: file: Use kzalloc_flex for aio_cmd</p>
<p>The target_core_file doesn't initialize the aio_cmd-&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-&gt;ki_write_stream &gt; max_write_streams
in the block device.</p>
<p>Let's just use kzalloc_flex when allocating the aio_cmd and let
ki_write_stream=0 to fix this issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-43055"/>
  </entry>
</feed>
