Linux
sched/psi: Shut down rtpoll_timer in psi_cgroup_free()
In the Linux kernel, the following vulnerability has been resolved: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() psi_schedule_rtpoll_work() is called locklessly from the scheduler hotpath and can race psi_trigger_destroy() taking down the last rtpoll trigger under rtpoll_trigger_lock: psi_schedule_rtpoll_work() psi_trigger_destroy() rcu_read_lock(); task = rcu_dereference(rtpoll_task); rcu_assign_pointer(rtpoll_task, NULL); timer_delete(&rtpoll_timer); mod_timer(&rtpoll_timer, ...); rcu_read_unlock(); synchronize_rcu(); kthread_stop(task_to_destroy); The group can then be freed with the re-armed timer still pending, and poll_timer_fn() runs on freed memory. 461daba06bdc ("psi: eliminate kthread_worker from psi trigger scheduling mechanism") deleted the timer synchronously after the synchronize_rcu(), which prevented this but raced trigger creation instead: the deletion could cancel the timer that a new trigger set armed during the grace period and, as creation also reinitialized the timer at the time, corrupt it. 8f91efd870ea ("psi: Fix race between psi_trigger_create/destroy") moved the initialization into group_init() and the deletion into the locked section, trading the creation races for the window above. Neither placement in the destruction path works. A pending timer firing while the group is alive is harmless though. poll_timer_fn() just wakes the rtpoll waitqueue and doesn't re-arm itself. Bind the timer to the group's lifetime instead and shut it down in psi_cgroup_free(). Nothing can arm it by then. timer_shutdown_sync() because the timer is never armed again.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6bfcb6178925b1fd28c102e53d403091b8f49396, < 4addb102154b7cf6e2310ccbe20c3c08619e520d
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 894a9300d7fb2e2951da92e565ae6de7ddfb0a69
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 1e5ca82eee59caca6988f9d6e859786aab8a5fa0
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 310b5a537a78c358a4cd244bd767c1a517a05459
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 8037c5b2b2a447df52542f4d8535895d837bdcbd
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 611e7821c4f83a671455658797336faecc3a5196
- >= 8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83, < 5457025fa8ca3c0d2732109513de839e3e797190
- e1e5e263bbe0e6e9c3db36aa48a3c8acf546fa49
- 979965c33f734a1666af67900408f997ac669c23
- >= 5.10.50, < 5.10.266
- >= 5.12.17, < 5.13
- >= 5.13.2, < 5.14
Fixed in 4addb102154b7cf6e2310ccbe20c3c08619e520d, 894a9300d7fb2e2951da92e565ae6de7ddfb0a69, 1e5ca82eee59caca6988f9d6e859786aab8a5fa0, 310b5a537a78c358a4cd244bd767c1a517a05459, 806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08, 8037c5b2b2a447df52542f4d8535895d837bdcbd, 611e7821c4f83a671455658797336faecc3a5196, 5457025fa8ca3c0d2732109513de839e3e797190, 5.10.266, 5.13, 5.14
- 5.14
Fixed in 0, 5.10.266, 5.15.217, 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9, 7.2
Mitigation
Upgrade Linux to 4addb102154b7cf6e2310ccbe20c3c08619e520d or 894a9300d7fb2e2951da92e565ae6de7ddfb0a69 or 1e5ca82eee59caca6988f9d6e859786aab8a5fa0 or 310b5a537a78c358a4cd244bd767c1a517a05459 or 806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08 or 8037c5b2b2a447df52542f4d8535895d837bdcbd or 611e7821c4f83a671455658797336faecc3a5196 or 5457025fa8ca3c0d2732109513de839e3e797190 or 5.10.266 or 5.13 or 5.14 or later.
Upgrade Linux to 0 or 5.10.266 or 5.15.217 or 6.1.183 or 6.6.152 or 6.12.104 or 6.18.45 or 7.1.9 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.