debugobjects: Do not fill_pool() if pi_blocked_on
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4bedcc28469a24fe481a8a31b3584e6070457ddb · < 5f41161059fd0f1bbf18c90f3180e38cc45a14eb| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
On RT-enabled Linux kernels, debugobjects can call fill_pool() while the current task has pi_blocked_on set, causing an assertion in rtlock_lock(). The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running RT-enabled Linux kernels should check whether their kernel includes the debugobjects fix; affected versions are not specified.