{"id":"DEBIAN-CVE-2024-27005","details":"In the Linux kernel, the following vulnerability has been resolved:  interconnect: Don't access req_list while it's being manipulated  The icc_lock mutex was split into separate icc_lock and icc_bw_lock mutexes in [1] to avoid lockdep splats. However, this didn't adequately protect access to icc_node::req_list.  The icc_set_bw() function will eventually iterate over req_list while only holding icc_bw_lock, but req_list can be modified while only holding icc_lock. This causes races between icc_set_bw(), of_icc_get(), and icc_put().  Example A:    CPU0                               CPU1   ----                               ----   icc_set_bw(path_a)     mutex_lock(&icc_bw_lock);                                      icc_put(path_b)                                        mutex_lock(&icc_lock);     aggregate_requests()       hlist_for_each_entry(r, ...                                        hlist_del(...         \u003cr = invalid pointer\u003e  Example B:    CPU0                               CPU1   ----                               ----   icc_set_bw(path_a)     mutex_lock(&icc_bw_lock);                                      path_b = of_icc_get()                                        of_icc_get_by_index()                                          mutex_lock(&icc_lock);                                          path_find()                                            path_init()     aggregate_requests()       hlist_for_each_entry(r, ...                                              hlist_add_head(...         \u003cr = invalid pointer\u003e  Fix this by ensuring icc_bw_lock is always held before manipulating icc_node::req_list. The additional places icc_bw_lock is held don't perform any memory allocations, so we should still be safe from the original lockdep splats that motivated the separate locks.  [1] commit af42269c3523 (\"interconnect: Fix locking for runpm vs reclaim\")","modified":"2026-09-15T09:03:05.981904863Z","published":"2024-05-01T06:15:18.883Z","upstream":["CVE-2024-27005"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2024-27005"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.9-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-27005.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.9-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2024-27005.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"}]}