CVE-2024-26627: scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
First published: Wed Mar 06 2024(Updated: )
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]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.10-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/07e3ca0f17f579491b5f54e9ed05173d6c1d6fcb
- https://git.kernel.org/stable/c/4373534a9850627a2695317944898eb1283a2db0
- https://git.kernel.org/stable/c/65ead8468c21c2676d4d06f50b46beffdea69df1
- https://git.kernel.org/stable/c/d37c1c81419fdef66ebd0747cf76fb8b7d979059
- https://git.kernel.org/stable/c/db6338f45971b4285ea368432a84033690eaf53c
- https://git.kernel.org/stable/c/f5944853f7a961fedc1227dc8f60393f8936d37c
- https://launchpad.net/bugs/cve/CVE-2024-26627
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26627
- https://nvd.nist.gov/vuln/detail/CVE-2024-26627
- https://security-tracker.debian.org/tracker/CVE-2024-26627
- https://ubuntu.com/security/CVE-2024-26627
- https://git.kernel.org/linus/4373534a9850627a2695317944898eb1283a2db0
Frequently Asked Questions
What is the severity of CVE-2024-26627?
CVE-2024-26627 is classified with a severity rating that indicates it could potentially impact system stability.
How do I fix CVE-2024-26627?
To fix CVE-2024-26627, update to one of the patched kernel versions such as 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, or 6.12.10-1.
What systems are affected by CVE-2024-26627?
CVE-2024-26627 affects systems running specific versions of the Linux kernel packages from Debian.
Is CVE-2024-26627 being actively exploited?
As of now, there is no evidence to suggest that CVE-2024-26627 is being actively exploited in the wild.
What are the implications of CVE-2024-26627 for users?
Users may face reduced system performance or stability issues due to the implications of CVE-2024-26627, warranting an update to mitigate risks.
- agent/title
- agent/type
- agent/author
- agent/remedy
- agent/first-publish-date
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/launchpad-cve
- source/Launchpad
- agent/severity
- collector/nvd-api
- source/NVD
- agent/references
- collector/nvd-cve
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- agent/tags
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- agent/softwarecombine
- agent/source
- package-manager/debian