RAID device failure via signed threshold overflow
Published Sep 16, 2025 · Updated Sep 16, 2025
Integer overflow in Linux kernel md/RAID10 allows local users to force a RAID device failure through the max_read_errors sysfs attribute. The max_corrected_read_errors_store function parses an unsigned value, then stores it in a signed atomic integer without rejecting values above INT_MAX, producing a negative threshold. Write access to the owner-writable attribute on a configured RAID10 array is required; a subsequent corrected read error can exceed the negative threshold and mark a mirror device faulty.
Summary
What happened
Integer overflow in Linux kernel md/RAID10 allows local users to force a RAID device failure through the max_read_errors sysfs attribute. The max_corrected_read_errors_store function parses an unsigned value, then stores it in a signed atomic integer without rejecting values above INT_MAX, producing a negative threshold. Write access to the owner-writable attribute on a configured RAID10 array is required; a subsequent corrected read error can exceed the negative threshold and mark a mirror device faulty.
The record
- CVE
- CVE-2023-53313
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- 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=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <025fde32fb957a5c271711bc66841f817ff5f299
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <05d10428e8dffed0bac2502f34151729fc189cd3
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <31c805a44b7569ca1017a4714385182d98bba212
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <3c76920e547d4b931bed758bad83fd658dd88b4e
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <74050a3fdd4aecfd2cbf74d3c145812ab2744375
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <aef6e98eb772594edd4399625e4e1bbe45971fa1
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <b1d8f38310bce3282374983b229d94edbaf1e570
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <e83cb411aa1c6c9617db9329897f4506ba9e9b9d
- Affected versionversion=1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d <f8b20a405428803bd9881881d8242c9d72c6b2b2
- Affected versionversion=2.6.33
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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