Service interruption via MD device-binding memory leak
Published Apr 17, 2024 · Updated May 11, 2026
Memory leak in the Linux kernel MD subsystem allows local users to exhaust kernel memory through failed MD device binding. In bind_rdev_to_array(), a failed kobject_add() leaves the rdev->serial allocation unfreed instead of releasing it on the error path. Local low-privileged access and a failing MD-device add operation are required; repeated triggers can interrupt system availability.
Summary
What happened
Memory leak in the Linux kernel MD subsystem allows local users to exhaust kernel memory through failed MD device binding. In bind_rdev_to_array(), a failed kobject_add() leaves the rdev->serial allocation unfreed instead of releasing it on the error path. Local low-privileged access and a failing MD-device add operation are required; repeated triggers can interrupt system availability.
The record
- CVE
- CVE-2024-26900
- Published
- Apr 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=5.3
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <4c1021ce46fc2fb6115f7e79d353941e6dcad366
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <6cf350658736681b9d6b0b6e58c5c76b235bb4c4
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <6d32c832a88513f65c2c2c9c75954ee8b387adea
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <9fd0198f7ef06ae0d6636fb0578560857dead995
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <beaf11969fd5cbe6f09cefaa34df1ce8578e8dd9
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <f3a1787dc48213f6caea5ba7d47e0222e7fa34a9
- Affected versionversion=963c555e75b033202dd76cf6325a7b7c83d08d5f <fb5b347efd1bda989846ffc74679d181222fb123
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