CVE-2026-53123
Last modified
CVE-2026-53123 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: md: wake raid456 reshape waiters before suspend During raid456 reshape, direct IO across the reshape position can sleep in raid5_make_request() waiting for reshape progress while still holding an active_io reference. If userspace then freezes reshape and writes md/suspend_lo or md/suspend_hi, mddev_suspend() kills active_io and waits for all in-flight IO to drain. This can deadlock: the IO needs reshape progress to continue, but the reshape thread is already frozen, so the active_io reference is never dropped and suspend never completes. raid5_prepare_suspend() already wakes wait_for_reshape for dm-raid. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: md: wake raid456 reshape waiters before suspend During raid456 reshape, direct IO across the reshape position can sleep in raid5_make_request() waiting for reshape progress while still holding an active_io reference. If userspace then freezes reshape and writes md/suspend_lo or md/suspend_hi, mddev_suspend() kills active_io and waits for all in-flight IO to drain. This can deadlock: the IO needs reshape progress to continue, but the reshape thread is already frozen, so the active_io reference is never dropped and suspend never completes. raid5_prepare_suspend() already wakes wait_for_reshape for dm-raid. Do the same for normal md suspend when reshape is already interrupted, so waiting raid456 IO can abort, drop its reference, and let suspend finish. The mdadm test tests/25raid456-reshape-deadlock reproduces the hang.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.7, < 6.12.91 |
| Linux | Linux Kernel | >= 6.13, < 6.18.33 |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53123?
How severe is CVE-2026-53123?
How do I fix CVE-2026-53123?
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 2026
- CVE-2026-53118In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53119In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5312A weakness has been identified in D-Link DNS-120, DNR-202L, …5.5
- CVE-2026-53120In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53121In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53122In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53124In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53126In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53129In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53123?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
