{"id":"CVE-2024-27005","title":"interconnect: Don't access req_list while it's being manipulated","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ninterconnect: Don't access req_list while it's being manipulated\n\nThe icc_lock mutex was split into separate icc_lock and icc_bw_lock\nmutexes in [1] to avoid lockdep sp…","severity":"high","cvss":7.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= 9be2957f014d91088db1eb5dd09d9a03d7184dce < fe549d8e976300d0dd75bd904eb216bed8b145e0","Linux >= ee42bfc791aa3cd78e29046f26a09d189beb3efb < 19ec82b3cad1abef2a929262b8c1528f4e0c192d","Linux >= ffb8917c70a4c88725ee40f9eeee9240ad1c1869 < 8401bc2c188030fb14d1cb43c402a1cf42d86dd2","Linux >= af42269c3523492d71ebbe11fefae2653e9cdc78 < d0d04efa2e367921654b5106cc5c05e3757c2b42","Linux >= af42269c3523492d71ebbe11fefae2653e9cdc78 < 4c65507121ea8e0b47fae6d2049c8688390d46b6","Linux >= af42269c3523492d71ebbe11fefae2653e9cdc78 < de1bf25b6d771abdb52d43546cf57ad775fb68a1","Linux 2f3a124696d43de3c837f87a9f767c56ee86cf2a","Linux >= 5.15.133 < 5.15.151","Linux >= 6.1.55 < 6.1.81","Linux >= 6.5.5 < 6.6","Linux 6.6"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2024-06-06T18:46:13.449387Z"},"published":"2024-05-01","updated":"2026-10-30","sourceUpdated":"2026-10-30T12:18:05.338Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-27005","references":[{"url":"https://git.kernel.org/stable/c/fe549d8e976300d0dd75bd904eb216bed8b145e0"},{"url":"https://git.kernel.org/stable/c/19ec82b3cad1abef2a929262b8c1528f4e0c192d"},{"url":"https://git.kernel.org/stable/c/8401bc2c188030fb14d1cb43c402a1cf42d86dd2"},{"url":"https://git.kernel.org/stable/c/d0d04efa2e367921654b5106cc5c05e3757c2b42"},{"url":"https://git.kernel.org/stable/c/4c65507121ea8e0b47fae6d2049c8688390d46b6"},{"url":"https://git.kernel.org/stable/c/de1bf25b6d771abdb52d43546cf57ad775fb68a1"}],"tags":["cve.org"],"epss":0.00189,"epssPercentile":0.08552,"ingestedAt":"2026-11-03T12:44:28.803Z","slug":"CVE-2024-27005","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninterconnect: Don't access req_list while it's being manipulated\n\nThe icc_lock mutex was split into separate icc_lock and icc_bw_lock\nmutexes in [1] to avoid lockdep splats. However, this didn't adequately\nprotect access to icc_node::req_list.\n\nThe icc_set_bw() function will eventually iterate over req_list while\nonly holding icc_bw_lock, but req_list can be modified while only\nholding icc_lock. This causes races between icc_set_bw(), of_icc_get(),\nand icc_put().\n\nExample A:\n\n  CPU0                               CPU1\n  ----                               ----\n  icc_set_bw(path_a)\n    mutex_lock(&icc_bw_lock);\n                                     icc_put(path_b)\n                                       mutex_lock(&icc_lock);\n    aggregate_requests()\n      hlist_for_each_entry(r, ...\n                                       hlist_del(...\n        <r = invalid pointer>\n\nExample B:\n\n  CPU0                               CPU1\n  ----                               ----\n  icc_set_bw(path_a)\n    mutex_lock(&icc_bw_lock);\n                                     path_b = of_icc_get()\n                                       of_icc_get_by_index()\n                                         mutex_lock(&icc_lock);\n                                         path_find()\n                                           path_init()\n    aggregate_requests()\n      hlist_for_each_entry(r, ...\n                                             hlist_add_head(...\n        <r = invalid pointer>\n\nFix this by ensuring icc_bw_lock is always held before manipulating\nicc_node::req_list. The additional places icc_bw_lock is held don't\nperform any memory allocations, so we should still be safe from the\noriginal lockdep splats that motivated the separate locks.\n\n[1] commit af42269c3523 (\"interconnect: Fix locking for runpm vs reclaim\")\n\n## Affected\n\n- `Linux >= 9be2957f014d91088db1eb5dd09d9a03d7184dce < fe549d8e976300d0dd75bd904eb216bed8b145e0`\n- `Linux >= ee42bfc791aa3cd78e29046f26a09d189beb3efb < 19ec82b3cad1abef2a929262b8c1528f4e0c192d`\n- `Linux >= ffb8917c70a4c88725ee40f9eeee9240ad1c1869 < 8401bc2c188030fb14d1cb43c402a1cf42d86dd2`\n- `Linux >= af42269c3523492d71ebbe11fefae2653e9cdc78 < d0d04efa2e367921654b5106cc5c05e3757c2b42`\n- `Linux >= af42269c3523492d71ebbe11fefae2653e9cdc78 < 4c65507121ea8e0b47fae6d2049c8688390d46b6`\n- `Linux >= af42269c3523492d71ebbe11fefae2653e9cdc78 < de1bf25b6d771abdb52d43546cf57ad775fb68a1`\n- `Linux 2f3a124696d43de3c837f87a9f767c56ee86cf2a`\n- `Linux >= 5.15.133 < 5.15.151`\n- `Linux >= 6.1.55 < 6.1.81`\n- `Linux >= 6.5.5 < 6.6`\n- `Linux 6.6`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":43,"depthScoreParts":{"impact":42.9,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}