LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26718: dm-crypt, dm-verity: disable tasklets

In the Linux kernel, the following vulnerability has been resolved: dm-crypt, dm-verity: disable tasklets Tasklets have an inherent problem with memory corruption. The function tasklet_action_common calls tasklet_trylock, then it calls the tasklet callback and then it calls tasklet_unlock. If the tasklet callback frees the structure that contains the tasklet or if it calls some code that may free it, tasklet_unlock will write into free memory. The commits 8e14f610159d and d9a02e016aaf try to fix it for dm-crypt, but it is not a sufficient fix and the data corruption can still happen [1]. There is no fix for dm-verity and dm-verity will write into free memory with every tasklet-processed bio. There will be atomic workqueues implemented in the kernel 6.9 [2]. They will have better interface and they will not suffer from the memory corruption problem. But we need something that stops the memory corruption now and that can be backported to the stable kernels. So, I'm proposing this commit that disables tasklets in both dm-crypt and dm-verity. This commit doesn't remove the tasklet support, because the tasklet code will be reused when atomic workqueues will be implemented. [1] https://lore.kernel.org/all/d390d7ee-f142-44d3-822a-87949e14608b@suse.de/T/ [2] https://lore.kernel.org/lkml/20240130091300.2968534-1-tj@kernel.org/

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw in dm-crypt and dm-verity can corrupt memory while processing storage activity. Systems using affected kernels and these device-mapper features may suffer data corruption, crashes, or broader compromise. The supplied CVSS assessment requires local, low-privileged access; this is not described as a remote attack.

Executive priority

Treat as a high-priority kernel maintenance issue for storage infrastructure using dm-crypt or dm-verity. Accelerate remediation where sensitive encrypted data, verified boot assets, or availability-critical workloads are involved. Broader fleet urgency depends on confirmed feature use and vendor package exposure; there is no supplied evidence of active exploitation.

Technical view

Tasklet callbacks can free their containing structure before tasklet_unlock writes to it, causing a use-after-free write. Earlier dm-crypt changes were insufficient, while dm-verity could trigger the condition for every tasklet-processed bio. The stable fix disables tasklets in both components pending a safer atomic-workqueue design.

Likely exposure

Exposure is concentrated in systems running affected Linux kernel versions with dm-crypt or dm-verity actively used. This may include encrypted-storage and verified-storage deployments. The supplied affected-version data is ambiguous, so downstream distribution package status and exact backports must be checked rather than relying only on upstream version numbers.

Exploitation context

The supplied CVSS vector indicates local access, low privileges, low complexity, and no user interaction, with potentially high confidentiality, integrity, and availability impact. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. Practical exploitability is not established by this bundle.

Researcher notes

The core condition is a tasklet lifetime error leading to a write after free. The source notes incomplete earlier dm-crypt fixes and a consistent dm-verity hazard for tasklet-processed bios. Five stable-kernel commits are supplied, likely reflecting branch-specific backports. Distribution kernels may diverge, and the bundle does not establish exploit reliability or observed attacks.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix or confirmed backport.
  • Prioritize hosts actively using dm-crypt or dm-verity for storage protection.
  • Reboot into the corrected kernel after installation and verify the running version.
  • If patching is delayed, consult distribution guidance for supported temporary mitigations.

Validation and detection

  • Inventory running kernel builds and identify downstream vendor backports.
  • Confirm whether dm-crypt or dm-verity is configured and actively processing storage I/O.
  • Check the installed kernel changelog for CVE-2024-26718 or the applicable stable commit.
  • After reboot, verify the corrected kernel is running across all affected hosts.
  • Review kernel logs and storage monitoring for crashes, corruption indicators, or device-mapper errors.
Prepared
Confidence
high
Sources
9

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-26718 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26718Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877, 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877unaffected
LinuxLinux5.9, 0, 5.15.169, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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