From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89599: fbdev: omapfb: panel-dsi-cm: initialize lock before registering display
Date: Fri, 11 Sep 2026 21:44:48 +0200 [thread overview]
Message-ID: <2026091132-CVE-2026-89599-895a@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
fbdev: omapfb: panel-dsi-cm: initialize lock before registering display
dsicm_probe() registers the display before initializing ddata->lock.
Once omapdss_register_display() publishes the display, another consumer
can reach a dsicm callback that takes this mutex while it is still
uninitialized.
Initialize the mutex before registering the display so the published
callbacks always see a valid lock.
The Linux kernel CVE team has assigned CVE-2026-89599 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.5 with commit f76ee892a99e68b55402b8d4b8aeffcae2aff34d and fixed in 6.12.109 with commit 2c3f8c9c995db185284b079f39177e85b2258176
Issue introduced in 4.5 with commit f76ee892a99e68b55402b8d4b8aeffcae2aff34d and fixed in 6.18.50 with commit 76818e81cfcae33b09b739de09162c7d8d89bf0b
Issue introduced in 4.5 with commit f76ee892a99e68b55402b8d4b8aeffcae2aff34d and fixed in 7.2.4 with commit 09db79078f25c048cfb5d7849795c70415ab8574
Issue introduced in 4.5 with commit f76ee892a99e68b55402b8d4b8aeffcae2aff34d and fixed in 7.3-rc1 with commit f8e43fe0f22b7137ce456e6fe3581d3098174f74
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-89599
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/omap2/omapfb/displays/panel-dsi-cm.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/2c3f8c9c995db185284b079f39177e85b2258176
https://git.kernel.org/stable/c/76818e81cfcae33b09b739de09162c7d8d89bf0b
https://git.kernel.org/stable/c/09db79078f25c048cfb5d7849795c70415ab8574
https://git.kernel.org/stable/c/f8e43fe0f22b7137ce456e6fe3581d3098174f74
reply other threads:[~2026-09-11 19:58 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-89599-895a@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