<?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>Sun, 04 Oct 2026 15:39:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43287 — drm: Account property blob allocations to memcg</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43287</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: Account property blob allocations to memcg&lt;/p&gt;
&lt;p&gt;DRM_IOCTL_MODE_CREATEPROPBLOB allows userspace to allocate arbitrary-sized
property blobs backed by kernel memory.&lt;/p&gt;
&lt;p&gt;Currently, the blob data allocation is not accounted to the allocating
process&amp;#39;s memory cgroup, allowing unprivileged users to trigger unbounded
kernel memory consumption and potentially cause system-wide OOM.&lt;/p&gt;
&lt;p&gt;Mark the property blob data allocation with GFP_KERNEL_ACCOUNT so that the memory
is properly charged to the caller&amp;#39;s memcg. This ensures existing cgroup
memory limits apply and prevents uncontrolled kernel memory growth without
introducing additional policy or per-file limits.&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: Account property blob allocations to memcg&lt;/p&gt;
&lt;p&gt;DRM_IOCTL_MODE_CREATEPROPBLOB allows userspace to allocate arbitrary-sized
property blobs backed by kernel memory.&lt;/p&gt;
&lt;p&gt;Currently, the blob data allocation is not accounted to the allocating
process&amp;#39;s memory cgroup, allowing unprivileged users to trigger unbounded
kernel memory consumption and potentially cause system-wide OOM.&lt;/p&gt;
&lt;p&gt;Mark the property blob data allocation with GFP_KERNEL_ACCOUNT so that the memory
is properly charged to the caller&amp;#39;s memcg. This ensures existing cgroup
memory limits apply and prevents uncontrolled kernel memory growth without
introducing additional policy or per-file limits.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43287</guid>
    </item>
  </channel>
</rss>
