<?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>Sat, 03 Oct 2026 10:58:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23149 — drm: Do not allow userspace to trigger kernel warnings in drm_gem_change_handle_ioctl()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23149</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: Do not allow userspace to trigger kernel warnings in drm_gem_change_handle_ioctl()&lt;/p&gt;
&lt;p&gt;Since GEM bo handles are u32 in the uapi and the internal implementation
uses idr_alloc() which uses int ranges, passing a new handle larger than
INT_MAX trivially triggers a kernel warning:&lt;/p&gt;
&lt;p&gt;idr_alloc():
...
	if (WARN_ON_ONCE(start &amp;lt; 0))
		return -EINVAL;
...&lt;/p&gt;
&lt;p&gt;Fix it by rejecting new handles above INT_MAX and at the same time make
the end limit calculation more obvious by moving into int domain.&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: Do not allow userspace to trigger kernel warnings in drm_gem_change_handle_ioctl()&lt;/p&gt;
&lt;p&gt;Since GEM bo handles are u32 in the uapi and the internal implementation
uses idr_alloc() which uses int ranges, passing a new handle larger than
INT_MAX trivially triggers a kernel warning:&lt;/p&gt;
&lt;p&gt;idr_alloc():
...
	if (WARN_ON_ONCE(start &amp;lt; 0))
		return -EINVAL;
...&lt;/p&gt;
&lt;p&gt;Fix it by rejecting new handles above INT_MAX and at the same time make
the end limit calculation more obvious by moving into int domain.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23149</guid>
    </item>
  </channel>
</rss>
