LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26860: dm-integrity: fix a memory leak when rechecking the data

In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix a memory leak when rechecking the data Memory for the "checksums" pointer will leak if the data is rechecked after checksum failure (because the associated kfree won't happen due to 'goto skip_io'). Fix this by freeing the checksums memory before recheck, and just use the "checksum_onstack" memory for storing checksum during recheck.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-26860 is a Linux kernel memory leak in dm-integrity. When data is rechecked after a checksum failure, allocated checksum memory may not be freed. The likely business concern is availability degradation on affected Linux systems using this storage integrity feature, but the source bundle provides no CVSS score or confirmed exploitation.

Executive priority

Treat as a kernel maintenance item with higher priority for storage-heavy or availability-critical Linux systems using dm-integrity. Current evidence does not support emergency response language, but unpatched kernel memory leaks can still affect reliability.

Technical view

The issue is in Linux kernel dm-integrity recheck handling. A checksum failure can send control flow to skip_io before freeing the checksums pointer, leaking memory. The fix frees checksum memory before recheck and uses checksum_onstack for recheck storage. Stable kernel fix commits are referenced.

Likely exposure

Exposure is most plausible on Linux hosts running affected kernel builds with dm-integrity in use. The bundle lists Linux kernel versions and stable commit references, but distro backports may change practical exposure. Systems not using dm-integrity are less likely to encounter the vulnerable path.

Exploitation context

The source bundle says this is not in KEV and provides no evidence of active exploitation. It describes a memory leak triggered during checksum failure recheck, not privilege escalation or remote code execution. Any exploitability beyond resource exhaustion is not established by the provided sources.

Researcher notes

The record lacks CVSS, CWE, and exploitation detail. Analysis should focus on affected kernel lineage, vendor backport status, and whether dm-integrity recheck paths are reachable in local deployments. Avoid assuming remote reachability or broader products without vendor evidence.

Mitigation direction

  • Apply Linux kernel updates from the operating system or appliance vendor.
  • Verify updates include one of the referenced stable kernel fixes.
  • Prioritize hosts using dm-integrity or storage integrity features.
  • If patching is delayed, follow vendor guidance for operational mitigations.
  • Monitor affected systems for abnormal kernel memory pressure.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Identify systems configured with dm-integrity or related device-mapper integrity targets.
  • Check vendor advisories or changelogs for CVE-2024-26860 coverage.
  • Confirm patched kernels include the referenced upstream stable commits.
  • Review monitoring for recurring checksum failures and memory growth.
Prepared
Confidence
medium
Sources
7

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-2024-26860 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
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux906414f4596469004632de29126c55751ed82c5e, d6824a28b244e8a750952848e4bd2167e1e9a17e, eb7b14a6a923c5678573c4d238c781cc83fcbc0f, c88f5e553fe38b2ffc4c33d08654e5281b297677, c88f5e553fe38b2ffc4c33d08654e5281b297677, 6.1.80, 6.6.19, 6.7.7unaffected
LinuxLinux6.8, 0, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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