<?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 22:25:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43442 — io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43442</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;io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops&lt;/p&gt;
&lt;p&gt;When IORING_SETUP_SQE_MIXED is used without IORING_SETUP_NO_SQARRAY,
the boundary check for 128-byte SQE operations in io_init_req()
validated the logical SQ head position rather than the physical SQE
index.&lt;/p&gt;
&lt;p&gt;The existing check:&lt;/p&gt;
&lt;p&gt;!(ctx-&amp;gt;cached_sq_head &amp;amp; (ctx-&amp;gt;sq_entries - 1))&lt;/p&gt;
&lt;p&gt;ensures the logical position isn&amp;#39;t at the end of the ring, which is
correct for NO_SQARRAY rings where physical == logical. However, when
sq_array is present, an unprivileged user can remap any logical
position to an arbitrary physical index via sq_array. Setting
sq_array[N] = sq_entries - 1 places a 128-byte operation at the last
physical SQE slot, causing the 128-byte memcpy in
io_uring_cmd_sqe_copy() to read 64 bytes past the end of the SQE
array.&lt;/p&gt;
&lt;p&gt;Replace the cached_sq_head alignment check with a direct validation
of the physical SQE index, which correctly handles both sq_array and
NO_SQARRAY cases.&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;io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops&lt;/p&gt;
&lt;p&gt;When IORING_SETUP_SQE_MIXED is used without IORING_SETUP_NO_SQARRAY,
the boundary check for 128-byte SQE operations in io_init_req()
validated the logical SQ head position rather than the physical SQE
index.&lt;/p&gt;
&lt;p&gt;The existing check:&lt;/p&gt;
&lt;p&gt;!(ctx-&amp;gt;cached_sq_head &amp;amp; (ctx-&amp;gt;sq_entries - 1))&lt;/p&gt;
&lt;p&gt;ensures the logical position isn&amp;#39;t at the end of the ring, which is
correct for NO_SQARRAY rings where physical == logical. However, when
sq_array is present, an unprivileged user can remap any logical
position to an arbitrary physical index via sq_array. Setting
sq_array[N] = sq_entries - 1 places a 128-byte operation at the last
physical SQE slot, causing the 128-byte memcpy in
io_uring_cmd_sqe_copy() to read 64 bytes past the end of the SQE
array.&lt;/p&gt;
&lt;p&gt;Replace the cached_sq_head alignment check with a direct validation
of the physical SQE index, which correctly handles both sq_array and
NO_SQARRAY cases.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43442</guid>
    </item>
  </channel>
</rss>
