# CVE-2024-26627: linux: In the Linux kernel, the following vulnerability has been resolved: scsi: core: Move scsi_host_busy() out of host lo... CVE-2024-26627 is fixed in 22 products on 1 platform, first by ALAS2023-2024-517, released February 15, 2024. It is not reported as exploited. Patch Radar priority: Routine. - Web page: https://patchblox.com/security/cve/CVE-2024-26627 - Priority: Routine - CVSS: 5.5 (medium) - EPSS: 0.0024 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Feb 15, 2024 ## Description In the Linux kernel, the following vulnerability has been resolved: scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler Inside scsi_eh_wakeup(), scsi_host_busy() is called & checked with host lock every time for deciding if error handler kthread needs to be waken up. This can be too heavy in case of recovery, such as: - N hardware queues - queue depth is M for each hardware queue - each scsi_host_busy() iterates over (N * M) tag/requests If recovery is triggered in case that all requests are in-flight, each scsi_eh_wakeup() is strictly serialized, when scsi_eh_wakeup() is called for the last in-flight request, scsi_host_busy() has been run for (N * M - 1) times, and request has been iterated for (N*M - 1) * (N * M) times. If both N and M are big enough, hard lockup can be triggered on acquiring host lock, and it is observed on mpi3mr(128 hw queues, queue depth 8169). Fix the issue by calling scsi_host_busy() outside the host lock. We don't need the host lock for getting busy count because host the lock never covers that. [mkp: Drop unnecessary 'busy' variables pointed out by Bart] ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | bpftool-debuginfo amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-debuginfo amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-debuginfo-common-aarch64 amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-debuginfo-common-x86_64 amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-devel amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-headers amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-libbpf amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-libbpf-devel amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-libbpf-static amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-livepatch-6.1.77-99.164 amzn 2023 | 1.0-0.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-modules-extra amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-modules-extra-common amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-tools amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-tools-debuginfo amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | kernel-tools-devel amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | linux Debian 12.15 (bookworm) | 6.1.82-1 | [DEBIAN-CVE-2024-26627](https://patchblox.com/security/data/fix/linux/debian-cve-2024-26627.md) | Mar 6, 2024 | | Linux | linux Debian 13.5 (trixie) | 6.7.7-1 | [DEBIAN-CVE-2024-26627](https://patchblox.com/security/data/fix/linux/debian-cve-2024-26627.md) | Mar 6, 2024 | | Linux | linux Debian 14 | 6.7.7-1 | [DEBIAN-CVE-2024-26627](https://patchblox.com/security/data/fix/linux/debian-cve-2024-26627.md) | Mar 6, 2024 | | Linux | perf amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | perf-debuginfo amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | python3-perf amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | | Linux | python3-perf-debuginfo amzn 2023 | 6.1.77-99.164.amzn2023 | [ALAS2023-2024-517](https://patchblox.com/security/data/fix/linux/alas2023-2024-517.md) | Feb 15, 2024 | --- Data as of 2026-11-09T01:18:40Z 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.