Kernel memory leak via orphaned RAID10 thread
Published Dec 30, 2025 · Updated Dec 30, 2025
Resource leak in affected Linux kernel releases allows attackers to retain kernel memory when RAID10 array setup fails. Within raid10_run(), setup_conf() creates conf->thread, but an error before mddev->thread is assigned bypasses cleanup and leaves that thread allocation unreleased. Reachability requires initiating RAID10 configuration and hitting the narrow setup-failure path; each successful trigger leaks kernel memory without reported code execution or data access.
Summary
What happened
Resource leak in affected Linux kernel releases allows attackers to retain kernel memory when RAID10 array setup fails. Within raid10_run(), setup_conf() creates conf->thread, but an error before mddev->thread is assigned bypasses cleanup and leaves that thread allocation unreleased. Reachability requires initiating RAID10 configuration and hitting the narrow setup-failure path; each successful trigger leaks kernel memory without reported code execution or data access.
The record
- CVE
- CVE-2023-54294
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 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=4.16
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <2a65555f7e0f4a05b663879908a991e6d9f81e51
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <36ba0c7b86acd9c2ea80a273204d52c21c955471
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <3725b35fc0e5e4eea0434ef625f3d92f3059d080
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <5d763f708b0f918fb87799e33c25113ae6081216
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <abf4d67060c8f63caff096e5fca1564bfef1e5d4
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <d6cfcf98b824591cffa4c1e9889fb4fa619359fe
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <ec473e82e10d39a02eb59b0b95e546119a3bdb79
- Affected versionversion=43a521238aca0e24d50add1db125a61bda2a3527 <f0ddb83da3cbbf8a1f9087a642c448ff52ee9abd
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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