Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 2 weeks, 2 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
debugobjects: Do not fill_pool() if pi_blocked_on

In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fill_pool() if pi_blocked_on On RT enabled kernels, fill_pool() ends up calling rtlock_lock(), which asserts if current::pi_blocked_on is set, because a task can obviously only block on one lock as otherwise the priority inheritenace chain gets corrupted. Prevent this by expanding the conditional to take current::pi_blocked_on into account.

Affected products

Linux
  • <5f41161059fd0f1bbf18c90f3180e38cc45a14eb
  • =<*
  • <33bee10644f8fff3b1a0187ad5ad34513e5e8e72
  • =<6.18.*
  • <5.15
  • =<7.0.*
  • ==5.15
  • <3a408cae608d9c075dd3a9e5cfc03b3cb0726863