Kernel memory leak via unreleased dm-integrity slab cache
Published Oct 4, 2025 · Updated Oct 4, 2025
Memory leak in Linux kernel dm-integrity allows attackers to consume kernel memory when device-mapper target registration fails. dm_integrity_init allocates journal_io_cache but returns from the dm_register_target failure path without calling kmem_cache_destroy. The flaw is limited to that local initialization failure path, and the public record does not establish how an attacker can induce repeated failures.
Summary
What happened
Memory leak in Linux kernel dm-integrity allows attackers to consume kernel memory when device-mapper target registration fails. dm_integrity_init allocates journal_io_cache but returns from the dm_register_target failure path without calling kmem_cache_destroy. The flaw is limited to that local initialization failure path, and the public record does not establish how an attacker can induce repeated failures.
The record
- CVE
- CVE-2023-53604
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3877b5c1509b16eeb1f275228fd91789cd88cf17
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <44f29e93a55b544dc961b6f8b4e93abaeaafb9ee
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6b79a428c02769f2a11f8ae76bf866226d134887
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d126899b0747305c9d39a0bcf87e0df9c3f555b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a5d8c6bf58e5b2e70fbc15f3b08dfc1ba6f269ac
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c8c9c50268729bf35f6c9bb1205f490db920454e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ca8b634fdf07dee3f6dfde57079c4511480b525e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e09a592fdd6c716506774bdbebb5f6c537b47767
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ff4d6b5b38429a7731e5593680d2138bf74dd546
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
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