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.
https://git.kernel.org/stable/c/f8e43fe0f22b7137ce456e6fe3581d3098174f74
https://git.kernel.org/stable/c/f33a96e49284589257e90ddc4394ec0c6bf11ec4
https://git.kernel.org/stable/c/ef20d4e17d7fb0d83144caa9667e6f3198288993
https://git.kernel.org/stable/c/e7023d18c4eb292f886b31a3576402cb0e357df7
https://git.kernel.org/stable/c/76818e81cfcae33b09b739de09162c7d8d89bf0b
https://git.kernel.org/stable/c/302d19fbc7dc7e9f498930c66d65ff711ba5ba9f
https://git.kernel.org/stable/c/2c3f8c9c995db185284b079f39177e85b2258176
https://git.kernel.org/stable/c/09db79078f25c048cfb5d7849795c70415ab8574