CVE-2024-27005

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(... <r = invalid pointer> 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(... <r = invalid pointer> 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")

• CWE-362
• CWE-667

• https://git.kernel.org/stable/c/19ec82b3cad1abef2a929262b8c1528f4e0c192d
• https://git.kernel.org/stable/c/4c65507121ea8e0b47fae6d2049c8688390d46b6Patch
• https://git.kernel.org/stable/c/d0d04efa2e367921654b5106cc5c05e3757c2b42Patch
• https://git.kernel.org/stable/c/de1bf25b6d771abdb52d43546cf57ad775fb68a1Patch
• https://git.kernel.org/stable/c/fe549d8e976300d0dd75bd904eb216bed8b145e0
• https://git.kernel.org/stable/c/4c65507121ea8e0b47fae6d2049c8688390d46b6Patch
• https://git.kernel.org/stable/c/d0d04efa2e367921654b5106cc5c05e3757c2b42Patch
• https://git.kernel.org/stable/c/de1bf25b6d771abdb52d43546cf57ad775fb68a1Patch
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4EZ6PJW7VOZ224TD7N4JZNU6KV32ZJ53/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DAMSOZXJEPUOXW33WZYWCVAY7Z5S7OOY/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GCBZZEC7L7KTWWAS2NLJK6SO3IZIL4WW/

Published

May 1, 2024

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-2700A vulnerability was found in the quarkus-core component. Qua…7
• CVE-2024-27000In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-27001In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27002In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27003In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27004In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27006In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27007In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27008In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-27009In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2024-27010In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-27011In the Linux kernel, the following vulnerability has been re…5.5