<?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>Fri, 02 Oct 2026 09:54:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43169 — drm/buddy: Prevent BUG_ON by validating rounded allocation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43169</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/buddy: Prevent BUG_ON by validating rounded allocation&lt;/p&gt;
&lt;p&gt;When DRM_BUDDY_CONTIGUOUS_ALLOCATION is set, the requested size is
rounded up to the next power-of-two via roundup_pow_of_two().
Similarly, for non-contiguous allocations with large min_block_size,
the size is aligned up via round_up(). Both operations can produce a
rounded size that exceeds mm-&amp;gt;size, which later triggers
BUG_ON(order &amp;gt; mm-&amp;gt;max_order).&lt;/p&gt;
&lt;p&gt;Example scenarios:
- 9G CONTIGUOUS allocation on 10G VRAM memory:
  roundup_pow_of_two(9G) = 16G &amp;gt; 10G
- 9G allocation with 8G min_block_size on 10G VRAM memory:
  round_up(9G, 8G) = 16G &amp;gt; 10G&lt;/p&gt;
&lt;p&gt;Fix this by checking the rounded size against mm-&amp;gt;size. For
non-contiguous or range allocations where size &amp;gt; mm-&amp;gt;size is invalid,
return -EINVAL immediately. For contiguous allocations without range
restrictions, allow the request to fall through to the existing
__alloc_contig_try_harder() fallback.&lt;/p&gt;
&lt;p&gt;This ensures invalid user input returns an error or uses the fallback
path instead of hitting BUG_ON.&lt;/p&gt;
&lt;p&gt;v2: (Matt A)
- Add Fixes, Cc stable, and Closes tags for context&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/buddy: Prevent BUG_ON by validating rounded allocation&lt;/p&gt;
&lt;p&gt;When DRM_BUDDY_CONTIGUOUS_ALLOCATION is set, the requested size is
rounded up to the next power-of-two via roundup_pow_of_two().
Similarly, for non-contiguous allocations with large min_block_size,
the size is aligned up via round_up(). Both operations can produce a
rounded size that exceeds mm-&amp;gt;size, which later triggers
BUG_ON(order &amp;gt; mm-&amp;gt;max_order).&lt;/p&gt;
&lt;p&gt;Example scenarios:
- 9G CONTIGUOUS allocation on 10G VRAM memory:
  roundup_pow_of_two(9G) = 16G &amp;gt; 10G
- 9G allocation with 8G min_block_size on 10G VRAM memory:
  round_up(9G, 8G) = 16G &amp;gt; 10G&lt;/p&gt;
&lt;p&gt;Fix this by checking the rounded size against mm-&amp;gt;size. For
non-contiguous or range allocations where size &amp;gt; mm-&amp;gt;size is invalid,
return -EINVAL immediately. For contiguous allocations without range
restrictions, allow the request to fall through to the existing
__alloc_contig_try_harder() fallback.&lt;/p&gt;
&lt;p&gt;This ensures invalid user input returns an error or uses the fallback
path instead of hitting BUG_ON.&lt;/p&gt;
&lt;p&gt;v2: (Matt A)
- Add Fixes, Cc stable, and Closes tags for context&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43169</guid>
    </item>
  </channel>
</rss>
