Vulnerability · Published Mar 6, 2024 · Assigned by Linux
CVE-2023-52587IB/ipoib: Fix mcast list locking
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 24% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: IB/ipoib: Fix mcast list locking Releasing the `priv->lock` while iterating the `priv->multicast_list` in `ipoib_mcast_join_task()` opens a window for `ipoib_mcast_dev_flush()` to remove the items while in the middle of iteration. If the mcast is removed while the lock was dropped, the for loop spins forever resulting in a hard lockup (as was reported on RHEL 4.18.0-372.75.1.el8_6 kernel): Task A (kworker/u72:2 below) | Task B (kworker/u72:0 below) -----------------------------------+----------------------------------- ipoib_mcast_join_task(work) | ipoib_ib_dev_flush_light(work) spin_lock_irq(&priv->lock) | __ipoib_ib_dev_flush(priv, ...) list_for_each_entry(mcast, | ipoib_mcast_dev_flush(dev = priv->dev) &priv->multicast_list, list) | ipoib_mcast_join(dev, mcast) | spin_unlock_irq(&priv->lock) | | spin_lock_irqsave(&priv->lock, flags) | list_for_each_entry_safe(mcast, tmcast, | &priv->multicast_list, list) | list_del(&mcast->list); | list_add_tail(&mcast->list, &remove_list) | spin_unlock_irqrestore(&priv->lock, flags) spin_lock_irq(&priv->lock) | | ipoib_mcast_remove_list(&remove_list) (Here, `mcast` is no longer on the | list_for_each_entry_safe(mcast, tmcast, `priv->multicast_list` and we keep | remove_list, list) spinning on the `remove_list` of | >>> wait_for_completion(&mcast->done) the other thread which is blocked | and the list is still valid on | it's stack.) Fix this by keeping the lock held and changing to GFP_ATOMIC to prevent eventual sleeps. Unfortunately we could not reproduce the lockup and confirm this fix but based on the code review I think this fix should address such lockups. crash> bc 31 PID: 747 TASK: ff1c6a1a007e8000 CPU: 31 COMMAND: "kworker/u72:2" -- [exception RIP: ipoib_mcast_join_task+0x1b1] RIP: ffffffffc0944ac1 RSP: ff646f199a8c7e00 RFLAGS: 00000002 RAX: 0000000000000000 RBX: ff1c6a1a04dc82f8 RCX: 0000000000000000 work (&priv->mcast_task{,.work}) RDX: ff1c6a192d60ac68 RSI: 0000000000000286 RDI: ff1c6a1a04dc8000 &mcast->list RBP: ff646f199a8c7e90 R8: ff1c699980019420 R9: ff1c6a1920c9a000 R10: ff646f199a8c7e00 R11: ff1c6a191a7d9800 R12: ff1c6a192d60ac00 mcast R13: ff1c6a1d82200000 R14: ff1c6a1a04dc8000 R15: ff1c6a1a04dc82d8 dev priv (&priv->lock) &priv->multicast_list (aka head) ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 --- <NMI exception stack> --- #5 [ff646f199a8c7e00] ipoib_mcast_join_task+0x1b1 at ffffffffc0944ac1 [ib_ipoib] #6 [ff646f199a8c7e98] process_one_work+0x1a7 at ffffffff9bf10967 crash> rx ff646f199a8c7e68 ff646f199a8c7e68: ff1c6a1a04dc82f8 <<< work = &priv->mcast_task.work crash> list -hO ipoib_dev_priv.multicast_list ff1c6a1a04dc8000 (empty) crash> ipoib_dev_priv.mcast_task.work.func,mcast_mutex.owner.counter ff1c6a1a04dc8000 mcast_task.work.func = 0xffffffffc0944910 <ipoib_mcast_join_task>, mcast_mutex.owner.counter = 0xff1c69998efec000 crash> b 8 PID: 8 TASK: ff1c69998efec000 CPU: 33 COMMAND: "kworker/u72:0" -- #3 [ff646f1980153d50] wait_for_completion+0x96 at ffffffff9c7d7646 #4 [ff646f1980153d90] ipoib_mcast_remove_list+0x56 at ffffffffc0944dc6 [ib_ipoib] #5 [ff646f1980153de8] ipoib_mcast_dev_flush+0x1a7 at ffffffffc09455a7 [ib_ipoib] #6 [ff646f1980153e58] __ipoib_ib_dev_flush+0x1a4 at ffffffffc09431a4 [ib_ipoib] #7 [ff ---truncated---
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.82-1 | DEBIAN-CVE-2023-52587 |
| Debian:13 | linux | 6.7.7-1 | DEBIAN-CVE-2023-52587 |
| Debian:14 | linux | 6.7.7-1 | DEBIAN-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux | 5.15.0-106.116 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux | 5.15.0-106.116 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1061.67 | USN-6766-3 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1061.67 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1063.72 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1063.72 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1022.23~22.04.1 | USN-6819-1 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1022.23~22.04.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1063.72.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1063.72.1 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1059.67 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1059.67 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1022.24~22.04.1 | USN-6818-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1022.24~22.04.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1058.63 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1058.63 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1044.51 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1044.51 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-41.41~22.04.2 | USN-6818-4 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-41.41~22.04.2 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1054.57 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1054.57 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1057.63 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1057.63 | USN-6795-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1058.63 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1058.63 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-106.116 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-106.116 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-41.41.1~22.04.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-41.41.1~22.04.1 | USN-6818-1 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1054.55 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1054.55 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1021.22 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1021.22 | USN-6818-3 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1026.26 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1015.15 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | 6.1.0-1035.35 | USN-6688-1 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | 6.1.0-1035.35 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1024.25 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1024.25 | USN-6819-3 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1059.65 | USN-6766-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1059.65 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1024.24~22.04.1 | USN-6819-4 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1024.24~22.04.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1054.57 | USN-6766-2 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1054.57 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | 6.5.0-40.40.1~22.04.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1015.16~22.04.1 | USN-6819-1 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1015.16~22.04.1 | UBUNTU-CVE-2023-52587 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1030.34 | UBUNTU-CVE-2023-52587 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before 4c8922ae8eb8dcc1e4b7d1059d97a8334288d825d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before 615e3adc2042b7be4ad122a043fc9135e6342c90d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before ac2630fd3c90ffec34a0bfc4d413668538b0e8f2d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before ed790bd0903ed3352ebf7f650d910f49b7319b34d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before 5108a2dc2db5630fb6cd58b8be80a0c134bc310ad2fe937ce6ce23daf5fb214e45432dbb631581b7 – before 342258fb46d66c1b4c7e2c3717ac01e10c03cf18d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before 7c7bd4d561e9dc6f5b7df9e184974915f6701a89d2fe937ce6ce23daf5fb214e45432dbb631581b7 – before 4f973e211b3b1c6d36f7c6a19239d258856749f9 |
| Linux | Linux | 4.1 |
References
- https://git.kernel.org/stable/c/4c8922ae8eb8dcc1e4b7d1059d97a8334288d825
- https://git.kernel.org/stable/c/615e3adc2042b7be4ad122a043fc9135e6342c90
- https://git.kernel.org/stable/c/ac2630fd3c90ffec34a0bfc4d413668538b0e8f2
- https://git.kernel.org/stable/c/ed790bd0903ed3352ebf7f650d910f49b7319b34
- https://git.kernel.org/stable/c/5108a2dc2db5630fb6cd58b8be80a0c134bc310a
- https://git.kernel.org/stable/c/342258fb46d66c1b4c7e2c3717ac01e10c03cf18
- https://git.kernel.org/stable/c/7c7bd4d561e9dc6f5b7df9e184974915f6701a89
- https://git.kernel.org/stable/c/4f973e211b3b1c6d36f7c6a19239d258856749f9
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html x_transferred
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html x_transferred