From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89597: fbdev: uvesafb: unregister connector callback on init failure
Date: Fri, 11 Sep 2026 21:44:46 +0200 [thread overview]
Message-ID: <2026091132-CVE-2026-89597-a7ca@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fbdev: uvesafb: unregister connector callback on init failure
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.
The later platform-device failure path already unregisters the callback.
Add the same cleanup before the final return when platform-driver
registration fails.
This issue was identified during our ongoing static-analysis research while
reviewing kernel code.
The Linux kernel CVE team has assigned CVE-2026-89597 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.24 with commit 8bdb3a2d7df48b861972c4bfb58490853a228f51 and fixed in 6.12.109 with commit 9f8a822b44c42502f105cf6574f4867067eecdd0
Issue introduced in 2.6.24 with commit 8bdb3a2d7df48b861972c4bfb58490853a228f51 and fixed in 6.18.50 with commit 466a8af0dee2cf745307155e26884e19a37b7e15
Issue introduced in 2.6.24 with commit 8bdb3a2d7df48b861972c4bfb58490853a228f51 and fixed in 7.2.4 with commit 9e768ae51426af2034d479133cfd73010d641b1a
Issue introduced in 2.6.24 with commit 8bdb3a2d7df48b861972c4bfb58490853a228f51 and fixed in 7.3-rc1 with commit de8db23aa7c337e606fca9faf48b3ba72968597a
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89597
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/video/fbdev/uvesafb.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/9f8a822b44c42502f105cf6574f4867067eecdd0
https://git.kernel.org/stable/c/466a8af0dee2cf745307155e26884e19a37b7e15
https://git.kernel.org/stable/c/9e768ae51426af2034d479133cfd73010d641b1a
https://git.kernel.org/stable/c/de8db23aa7c337e606fca9faf48b3ba72968597a
reply other threads:[~2026-09-11 19:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091132-CVE-2026-89597-a7ca@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox