LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53604: dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path

In the Linux kernel, the following vulnerability has been resolved: dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path Otherwise the journal_io_cache will leak if dm_register_target() fails.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel cleanup bug in the device-mapper integrity component. If initialization fails at a specific point, kernel memory allocated for journal I/O is not released. The source bundle does not show active exploitation, CVSS scoring, or direct data compromise.

Executive priority

Handle through normal kernel patch management unless dm-integrity is widely used or custom kernels are deployed. No evidence in the bundle supports emergency response or active exploitation.

Technical view

The issue is in dm_integrity_init(): if dm_register_target() fails, journal_io_cache is leaked because kmem_cache_destroy() was missing from the error path. Kernel stable commits add the missing cleanup. Evidence points to a memory leak during failure handling, not a complete exploit chain.

Likely exposure

Exposure is most relevant to Linux systems with kernels in the listed affected ranges and device-mapper integrity support. Practical exposure depends on whether dm-integrity is present, enabled, or packaged in the running kernel.

Exploitation context

The bundle says KEV is false and provides no source claiming active exploitation. It also provides no public exploit details. Impact appears limited to kernel memory leakage when dm_register_target() fails during dm-integrity initialization.

Researcher notes

The public description is narrow: a missing kmem_cache_destroy() call in an initialization error path. Version data in the bundle is incomplete for precise downstream distro mapping, so validate against vendor kernel advisories and commit backports.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable commits.
  • Prioritize systems using dm-integrity or custom kernel builds.
  • Check Linux distribution advisories for CVE-2023-53604 status.
  • Reboot systems after kernel update to load the fixed kernel.

Validation and detection

  • Inventory running Linux kernel versions against vendor advisories.
  • Confirm dm-integrity support is present or loaded on affected hosts.
  • Verify installed kernel changelogs reference CVE-2023-53604 or listed commits.
  • Confirm hosts are running the updated kernel after reboot.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53604 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
10Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14, 7eada909bfd7ac90a4522e56aa3179d1fd68cd14unaffected
LinuxLinux4.12, 0, 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.