Look up another CVE · open CVE-2026-89599 in the interactive tracker
CVE-2026-89599
fbdev: omapfb: panel-dsi-cm: initialize lock before registering display
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem drivers/video. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-89599 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.c
- What this is
- OMAP DISPLAY SUBSYSTEM and FRAMEBUFFER SUPPORT (DSS2)MAINTAINERS section matched on drivers/video/fbdev/omap2/ · linux-omap@vger.kernel.org · Orphan
- Kernel module
- none to look for. The file would have gone into panel_dsi_cm, and Debian does not compile it into that module, so finding panel_dsi_cm in lsmod would say nothing about this CVE.
Check it on the machine
grep -w CONFIG_FB_OMAP2_PANEL_DSI_CM /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 5 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sid, bookworm · linux-6.12n
- n
- not enabled on any flavour - this release does not build the code
- Build switch
- CONFIG_FB_OMAP2_PANEL_DSI_CM
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-11 (37 days ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 3.1% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/video
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.5 | 5.10.270 | ef20d4e17d7f |
| 4.5 | 5.15.221 | e7023d18c4eb |
| 4.5 | 6.1.188 | f33a96e49284 |
| 4.5 | 6.6.157 | 302d19fbc7dc |
| 4.5 | 6.12.109 | 2c3f8c9c995d |
| 4.5 | 6.18.50 | 76818e81cfca |
| 4.5 | 7.2.4 | 09db79078f25 |
| 4.5 | 7.3 | f8e43fe0f22b |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is in the OMAP DSI command-mode panel driver: dsicm_probe() publishes dsicm_ops via omapdss_register_display(), and those callbacks are reached from local omapfb probe, FBIOBLANK, and omapfb ioctls on /dev/fb*. There is no network, Bluetooth/WiFi, or USB protocol path into this code.
- AC:LAttack complexity, low
- On preemptible kernels dsicm_probe() can be preempted after omapdss_register_display() adds the panel to panel_list and before mutex_init(&ddata->lock). Concurrent omapfb_probe then calls dsicm_enable/enable_te/update on that published device, so the race is driven by the in-kernel consumer rather than an uninfluenced hardware lottery.
- PR:NPrivileges required, none
- dsicm_probe() and the omapfb consumer (omapfb_init_display → driver->enable/update) run from platform/deferred probe during boot on boards with an omapdss,panel-dsi-cm node. That path has no capable() or credential check and needs no OS account.
- UI:NUser interaction, none
- Display registration and omapfb’s subsequent enable/update run automatically during device enumeration on affected TI OMAP systems; no victim must open /dev/fb*, write sysfs, or mount a filesystem.
- S:UScope, unchanged
- Uninitialized-mutex use and any follow-on lock or DSI-state corruption remain inside the host omapfb/omapdss driver. This is not a VM escape, IOMMU bypass, or other cross-authority impact.
- C:HConfidentiality impact, high
- A consumer that wins the race mutex_lock()s kzalloc’d ddata->lock (NULL wait_list); probe can then mutex_init() a lock another thread still holds so two threads enter dsicm_enable/update. That lock-state corruption is kernel memory-unsafety that can be leveraged for disclosure, not a small bounded leak.
- I:HIntegrity impact, high
- mutex_init() of a mutex another thread still holds resets owner and wait_list while dsicm callbacks run unsynchronized against DSI bus and panel_drv_data state, giving write and control-flow primitives rather than a pure crash.
- A:HAvailability impact, high
- CONFIG_DEBUG_MUTEXES treats lock-used-without-init as an oops, and a corrupted mutex wait_list or double-entry into DSI enable/disable causes a kernel oops, panic, or hang, fully denying availability.