<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T11:04:27.250376+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-46209</id>
    <title>CVE-2026-46209 — drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()</title>
    <updated>2026-10-01T11:04:27.252280+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/gem: Fix inconsistent plane dimension calculation in drm_gem_fb_init_with_funcs()</p>
<p>drm_gem_fb_init_with_funcs() computes sub-sampled plane dimensions
using plain integer division:</p>
<p>unsigned int width  = mode_cmd-&gt;width  / (i ? info-&gt;hsub : 1);
  unsigned int height = mode_cmd-&gt;height / (i ? info-&gt;vsub : 1);</p>
<p>However, the ioctl-level framebuffer_check() in drm_framebuffer.c uses
drm_format_info_plane_width/height() which round up dimensions via
DIV_ROUND_UP(). This inconsistency corrupts the subsequent GEM object
size check for certain pixel format and dimension combinations.</p>
<p>For example, with NV12 (vsub=2) and a 1-pixel-tall framebuffer the
GEM size validation path sees height=0 instead of height=1. The
expression (height - 1) then wraps to UINT_MAX as an unsigned int,
causing min_size to overflow and wrap back to a small value. A tiny
GEM object therefore passes the size guard, yet when the GPU accesses
the chroma plane it will read or write memory beyond the object's
bounds.</p>
<p>Fix by replacing the open-coded divisions with drm_format_info_plane_width()
and drm_format_info_plane_height(), which use DIV_ROUND_UP() and match
the calculation already used in framebuffer_check().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-46209"/>
  </entry>
</feed>
