<?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 17:21:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53187 — RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53187</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/core: Validate cpu_id against nr_cpu_ids in DMAH alloc&lt;/p&gt;
&lt;p&gt;The cpu_id attribute supplied by user space through
UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumask_test_cpu()
without first verifying that the value is within the valid CPU range.&lt;/p&gt;
&lt;p&gt;Passing such untrusted data to cpumask_test_cpu() may lead to an
out-of-bounds read of the underlying cpumask bitmap: the helper expands
to a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with
no bound check.&lt;/p&gt;
&lt;p&gt;In addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trips
the WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this
turns a bad user input into a machine reboot.&lt;/p&gt;
&lt;p&gt;Reject any cpu_id that is not smaller than nr_cpu_ids with -EINVAL
before it is used.&lt;/p&gt;
&lt;p&gt;Reported by Smatch.&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/core: Validate cpu_id against nr_cpu_ids in DMAH alloc&lt;/p&gt;
&lt;p&gt;The cpu_id attribute supplied by user space through
UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumask_test_cpu()
without first verifying that the value is within the valid CPU range.&lt;/p&gt;
&lt;p&gt;Passing such untrusted data to cpumask_test_cpu() may lead to an
out-of-bounds read of the underlying cpumask bitmap: the helper expands
to a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with
no bound check.&lt;/p&gt;
&lt;p&gt;In addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trips
the WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this
turns a bad user input into a machine reboot.&lt;/p&gt;
&lt;p&gt;Reject any cpu_id that is not smaller than nr_cpu_ids with -EINVAL
before it is used.&lt;/p&gt;
&lt;p&gt;Reported by Smatch.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53187</guid>
    </item>
  </channel>
</rss>
