fbdev: omapfb: panel-dsi-cm: initialize lock before registering display
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f76ee892a99e68b55402b8d4b8aeffcae2aff34d · < 76818e81cfcae33b09b739de09162c7d8d89bf0b| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's panel-dsi-cm driver registers a display before initializing its mutex. A consumer that reaches a display callback during that interval can access the uninitialized mutex. The input does not specify whether this requires network access, authentication, or user interaction.
Engineers running Linux kernels with the omapfb panel-dsi-cm driver should check their versions; affected versions are not specified.