In the Linux kernel, the following vulnerability has been resolved:

rtmutex: Drop rt_mutex::wait_lock before scheduling

rt_mutex_handle_deadlock() is called with rt_mutex::wait_lock held.  In the
good case it returns with the lock held and in the deadlock case it emits a
warning and goes into an endless scheduling loop with the lock held, which
triggers the 'scheduling in atomic' warning.

Unlock rt_mutex::wait_lock in the dead lock case before issuing the warning
and dropping into the schedule for ever loop.

[ tglx: Moved unlock before the WARN(), removed the pointless comment,
  	massaged changelog, added Fixes tag ]

kernel.org https://git.kernel.org/stable/c/1401da1486dc1cdbef6025fd74a3977df3a3e5d0 [No types assigned]

kernel.org https://git.kernel.org/stable/c/432efdbe7da5ecfcbc0c2180cfdbab1441752a38 [No types assigned]

kernel.org https://git.kernel.org/stable/c/6a976e9a47e8e5b326de671811561cab12e6fb1f [No types assigned]

kernel.org https://git.kernel.org/stable/c/85f03ca98e07cd0786738b56ae73740bce0ac27f [No types assigned]

kernel.org https://git.kernel.org/stable/c/93f44655472d9cd418293d328f9d141ca234ad83 [No types assigned]

kernel.org https://git.kernel.org/stable/c/a92d81c9efec9280681c27a2c0a963fd0f1338e0 [No types assigned]

kernel.org https://git.kernel.org/stable/c/d33d26036a0274b472299d7dcdaa5fb34329f91b [No types assigned]

kernel.org https://git.kernel.org/stable/c/f13b5afc5c4889569d84c3011ce449f61fccfb28 [No types assigned]