I/O hang via leaked RAID10 recovery counter
Published Sep 16, 2025 · Updated Sep 16, 2025
Denial of service in the Linux kernel md/raid10 recovery path allows local users to hang I/O after a read failure. raid10_sync_request() increments r10bio->remaining for both the member and replacement bios, but recovery_request_write() returns without issuing failed-read writes, leaving only one completion decrement. Reachability requires an active RAID10 recovery and a member read failure; the resulting leaked counter prevents the recovery I/O from completing.
Summary
What happened
Denial of service in the Linux kernel md/raid10 recovery path allows local users to hang I/O after a read failure. raid10_sync_request() increments r10bio->remaining for both the member and replacement bios, but recovery_request_write() returns without issuing failed-read writes, leaving only one completion decrement. Reachability requires an active RAID10 recovery and a member read failure; the resulting leaked counter prevents the recovery I/O from completing.
The record
- CVE
- CVE-2023-53299
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <11141630f03efffdfe260b3582b2d93d38171b97
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <1697fb124c6d6c5237e9cbd78890310154738084
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <1d2c6c6e37fe5de11fd01a82badf03390e12df7a
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <26208a7cffd0c7cbf14237ccd20c7270b3ffeb7e
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <3481dec5ecbbbbe44ab23e22c2b14bd65c644ec6
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <4f82e7e07cdaf2947d71968e3d6b73370a217093
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <8c5d5d7ffd1e76734811b8ea5417cf0432b9952c
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <8d09065802c53cc938d162b62f6c4150b392c90e
- Affected versionversion=24afd80d99f80a79d8824d2805114b8b067e9823 <cb827ed2bb34480dc102146d3a1f89fdbcafc028
- Affected versionversion=3.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo