<?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>Thu, 01 Oct 2026 15:31:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23468 — drm/amdgpu: Limit BO list entry count to prevent resource exhaustion</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23468</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;drm/amdgpu: Limit BO list entry count to prevent resource exhaustion&lt;/p&gt;
&lt;p&gt;Userspace can pass an arbitrary number of BO list entries via the
bo_number field. Although the previous multiplication overflow check
prevents out-of-bounds allocation, a large number of entries could still
cause excessive memory allocation (up to potentially gigabytes) and
unnecessarily long list processing times.&lt;/p&gt;
&lt;p&gt;Introduce a hard limit of 128k entries per BO list, which is more than
sufficient for any realistic use case (e.g., a single list containing all
buffers in a large scene). This prevents memory exhaustion attacks and
ensures predictable performance.&lt;/p&gt;
&lt;p&gt;Return -EINVAL if the requested entry count exceeds the limit&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 688b87d39e0aa8135105b40dc167d74b5ada5332)&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;drm/amdgpu: Limit BO list entry count to prevent resource exhaustion&lt;/p&gt;
&lt;p&gt;Userspace can pass an arbitrary number of BO list entries via the
bo_number field. Although the previous multiplication overflow check
prevents out-of-bounds allocation, a large number of entries could still
cause excessive memory allocation (up to potentially gigabytes) and
unnecessarily long list processing times.&lt;/p&gt;
&lt;p&gt;Introduce a hard limit of 128k entries per BO list, which is more than
sufficient for any realistic use case (e.g., a single list containing all
buffers in a large scene). This prevents memory exhaustion attacks and
ensures predictable performance.&lt;/p&gt;
&lt;p&gt;Return -EINVAL if the requested entry count exceeds the limit&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 688b87d39e0aa8135105b40dc167d74b5ada5332)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23468</guid>
    </item>
  </channel>
</rss>
