srcu: Use irq_work to start GP in tiny SRCU
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.576.19.147.0In the Linux kernel, the following vulnerability has been resolved:
srcu: Use irq_work to start GP in tiny SRCU
Tiny SRCU's srcu_gp_start_if_needed() directly calls schedule_work(), which acquires the workqueue pool->lock.
This causes a lockdep splat when call_srcu() is called with a scheduler lock held, due to:
call_srcu() [holding pi_lock] srcu_gp_start_if_needed() schedule_work() -> pool->lock
workqueue_init() / create_worker() [holding pool->lock] wake_up_process() -> try_to_wake_up() -> pi_lock
Also add irq_work_sync() to cleanup_srcu_struct() to prevent a use-after-free if a queued irq_work fires after cleanup begins.
Tested with rcutorture SRCU-T and no lockdep warnings.
From the CVE record · Linux
Tiny SRCU can trigger a lock-order warning when call_srcu() runs while a scheduler lock is held. Queued irq_work can also cause a use-after-free if it fires after SRCU cleanup begins. The input does not establish whether an attacker can trigger either condition or specify access requirements.
Engineers running Linux kernels that use tiny SRCU should check their kernel versions against the vendor advisory; affected versions were not provided.