# CVE-2024-27005: interconnect: Don't access req_list while it's being manipulated

CVE-2024-27005 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2024-27005, released May 1, 2024. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2024-27005
- Priority: High
- CVSS: 7.8 (Moderate)
- EPSS: 0.0019
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: May 1, 2024
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-27005

## Description

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")

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-azure sles 15.7 | 6.4.0-150700.20.27.1 | [SUSE-SU-2026:0472-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0472-1.md) | Feb 12, 2026 |
| Linux | kernel-default sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.31.1.150700.17.21.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-livepatch-SLE15-SP7-RT_Update_9 sles 15.7 | 1-150700.1.3.2 | [SUSE-SU-2026:0587-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0587-1.md) | Feb 20, 2026 |
| Linux | kernel-livepatch-SLE15-SP7_Update_9 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-source sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-source-azure sles 15.7 | 6.4.0-150700.20.27.1 | [SUSE-SU-2026:0472-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0472-1.md) | Feb 12, 2026 |
| Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | kernel-syms-azure sles 15.7 | 6.4.0-150700.20.27.1 | [SUSE-SU-2026:0472-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0472-1.md) | Feb 12, 2026 |
| Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.31.1 | [SUSE-SU-2026:0447-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-0447-1.md) | Feb 11, 2026 |
| Linux | linux Debian 13.5 (trixie) | 6.8.9-1 | [DEBIAN-CVE-2024-27005](https://patchblox.com/security/data/fix/linux/debian-cve-2024-27005.md) | May 1, 2024 |
| Linux | linux Debian 14 | 6.8.9-1 | [DEBIAN-CVE-2024-27005](https://patchblox.com/security/data/fix/linux/debian-cve-2024-27005.md) | May 1, 2024 |

---

Data as of 2026-11-08T00:53:09Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
