CVE-2024-26755
Last modified
CVE-2024-26755 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: md: Don't suspend the array for interrupted reshape md_start_sync() will suspend the array if there are spares that can be added or removed from conf, however, if reshape is still in progress, this won't happen at all or data will be corrupted(remove_and_add_spares won't be called from md_choose_sync_action for reshape), hence there is no need to suspend the array if reshape is not done yet. Meanwhile, there is a potential deadlock for raid456: 1) reshape is interrupted; 2) set one of the disk WantReplacement, and add a new disk to the array, however, recovery won't start until the reshape is finished; 3) then issue an IO across reshpae position, this IO will wait for reshape to make progress; 4) continue to reshape, then md_start_sync() found there is a spare disk that can be added to conf, mddev_suspend() is called; Step 4 and step 3 is waiting for each other, deadlock triggered. Noted this problem is found by code review, and it's not reporduced yet. Fix this porblem by don't suspend the array for interrupted reshape, this is safe because conf won't be changed until reshape is done.. EPSS estimates a 0.65% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: md: Don't suspend the array for interrupted reshape md_start_sync() will suspend the array if there are spares that can be added or removed from conf, however, if reshape is still in progress, this won't happen at all or data will be corrupted(remove_and_add_spares won't be called from md_choose_sync_action for reshape), hence there is no need to suspend the array if reshape is not done yet. Meanwhile, there is a potential deadlock for raid456: 1) reshape is interrupted; 2) set one of the disk WantReplacement, and add a new disk to the array, however, recovery won't start until the reshape is finished; 3) then issue an IO across reshpae position, this IO will wait for reshape to make progress; 4) continue to reshape, then md_start_sync() found there is a spare disk that can be added to conf, mddev_suspend() is called; Step 4 and step 3 is waiting for each other, deadlock triggered. Noted this problem is found by code review, and it's not reporduced yet. Fix this porblem by don't suspend the array for interrupted reshape, this is safe because conf won't be changed until reshape is done.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.7, < 6.7.7 | — |
| Linux | Linux Kernel | 6.8 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-26755?
How severe is CVE-2024-26755?
How do I fix CVE-2024-26755?
How Strix Helps
- 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.
Related CVEs from 2024
- CVE-2024-2675A vulnerability, which was classified as critical, has been …6.5
- CVE-2024-26750In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26751In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26752In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26753In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26754In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26756In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26757In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26758In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26759In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2676A vulnerability, which was classified as critical, was found…6.5
- CVE-2024-26760In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-26755?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
