<?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-09-30T11:43:50.977620+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-89597</id>
    <title>CVE-2026-89597 — fbdev: uvesafb: unregister connector callback on init failure</title>
    <updated>2026-09-30T11:43:51.072381+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>fbdev: uvesafb: unregister connector callback on init failure</p>
<p>uvesafb_init() registers the v86d connector callback before registering
the platform driver. If platform_driver_register() fails, the function
returns the error directly and leaves the connector callback registered.</p>
<p>The later platform-device failure path already unregisters the callback.
Add the same cleanup before the final return when platform-driver
registration fails.</p>
<p>This issue was identified during our ongoing static-analysis research while
reviewing kernel code.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89597"/>
  </entry>
</feed>
