<?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>Wed, 30 Sep 2026 23:05:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53403 — fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53403</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;fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var&lt;/p&gt;
&lt;p&gt;info-&amp;gt;var, a framebuffer&amp;#39;s current mode, is expected to have a matching
entry in info-&amp;gt;modelist. var_to_display() relies on this and treats a
failed fb_match_mode() as &amp;#34;This should not happen&amp;#34;. fb_set_var() keeps it
true by adding the mode to the list on every change, and
do_register_framebuffer() does the same at registration.&lt;/p&gt;
&lt;p&gt;store_modes() replaces the modelist from userspace. fb_new_modelist()
validates the new modes but does not check that info-&amp;gt;var still has a
match. It relies on fbcon_new_modelist() to re-point consoles, but that
only handles consoles mapped to the framebuffer. With fbcon unbound there
are none, so info-&amp;gt;var is left describing a mode that is no longer in the
list.&lt;/p&gt;
&lt;p&gt;A later console takeover runs var_to_display(), where fb_match_mode()
returns NULL and leaves fb_display[i].mode NULL. fbcon_switch() passes it
to display_to_var(), and fb_videomode_to_var() dereferences the NULL mode.&lt;/p&gt;
&lt;p&gt;Keep the current mode in the list in fb_new_modelist(), the same way
fb_set_var() does.&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;fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var&lt;/p&gt;
&lt;p&gt;info-&amp;gt;var, a framebuffer&amp;#39;s current mode, is expected to have a matching
entry in info-&amp;gt;modelist. var_to_display() relies on this and treats a
failed fb_match_mode() as &amp;#34;This should not happen&amp;#34;. fb_set_var() keeps it
true by adding the mode to the list on every change, and
do_register_framebuffer() does the same at registration.&lt;/p&gt;
&lt;p&gt;store_modes() replaces the modelist from userspace. fb_new_modelist()
validates the new modes but does not check that info-&amp;gt;var still has a
match. It relies on fbcon_new_modelist() to re-point consoles, but that
only handles consoles mapped to the framebuffer. With fbcon unbound there
are none, so info-&amp;gt;var is left describing a mode that is no longer in the
list.&lt;/p&gt;
&lt;p&gt;A later console takeover runs var_to_display(), where fb_match_mode()
returns NULL and leaves fb_display[i].mode NULL. fbcon_switch() passes it
to display_to_var(), and fb_videomode_to_var() dereferences the NULL mode.&lt;/p&gt;
&lt;p&gt;Keep the current mode in the list in fb_new_modelist(), the same way
fb_set_var() does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53403</guid>
    </item>
  </channel>
</rss>
