<?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>Wed, 30 Sep 2026 23:23:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45856 — RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-45856</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;RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send&lt;/p&gt;
&lt;p&gt;ib_uverbs_post_send() uses cmd.wqe_size from userspace without any
validation before passing it to kmalloc() and using the allocated
buffer as struct ib_uverbs_send_wr.&lt;/p&gt;
&lt;p&gt;If a user provides a small wqe_size value (e.g., 1), kmalloc() will
succeed, but subsequent accesses to user_wr-&amp;gt;opcode, user_wr-&amp;gt;num_sge,
and other fields will read beyond the allocated buffer, resulting in
an out-of-bounds read from kernel heap memory. This could potentially
leak sensitive kernel information to userspace.&lt;/p&gt;
&lt;p&gt;Additionally, providing an excessively large wqe_size can trigger a
WARNING in the memory allocation path, as reported by syzkaller.&lt;/p&gt;
&lt;p&gt;This is inconsistent with ib_uverbs_unmarshall_recv() which properly
validates that wqe_size &amp;gt;= sizeof(struct ib_uverbs_recv_wr) before
proceeding.&lt;/p&gt;
&lt;p&gt;Add the same validation for ib_uverbs_post_send() to ensure wqe_size
is at least sizeof(struct ib_uverbs_send_wr).&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;RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send&lt;/p&gt;
&lt;p&gt;ib_uverbs_post_send() uses cmd.wqe_size from userspace without any
validation before passing it to kmalloc() and using the allocated
buffer as struct ib_uverbs_send_wr.&lt;/p&gt;
&lt;p&gt;If a user provides a small wqe_size value (e.g., 1), kmalloc() will
succeed, but subsequent accesses to user_wr-&amp;gt;opcode, user_wr-&amp;gt;num_sge,
and other fields will read beyond the allocated buffer, resulting in
an out-of-bounds read from kernel heap memory. This could potentially
leak sensitive kernel information to userspace.&lt;/p&gt;
&lt;p&gt;Additionally, providing an excessively large wqe_size can trigger a
WARNING in the memory allocation path, as reported by syzkaller.&lt;/p&gt;
&lt;p&gt;This is inconsistent with ib_uverbs_unmarshall_recv() which properly
validates that wqe_size &amp;gt;= sizeof(struct ib_uverbs_recv_wr) before
proceeding.&lt;/p&gt;
&lt;p&gt;Add the same validation for ib_uverbs_post_send() to ensure wqe_size
is at least sizeof(struct ib_uverbs_send_wr).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-45856</guid>
    </item>
  </channel>
</rss>
