LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50843: dm clone: Fix UAF in clone_dtr()

In the Linux kernel, the following vulnerability has been resolved: dm clone: Fix UAF in clone_dtr() Dm_clone also has the same UAF problem when dm_resume() and dm_destroy() are concurrent. Therefore, cancelling timer again in clone_dtr().

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50843 is a Linux kernel use-after-free flaw in the device-mapper clone component. It occurs during a race between resume and destroy operations. Public sources do not provide a CVSS score, confirmed exploitation, or a complete impact statement, so urgency depends on whether affected kernels and dm-clone are present.

Executive priority

Treat as a kernel maintenance item with unknown severity. Prioritize systems using device-mapper clone or running older affected kernels, but avoid emergency response unless your vendor assigns higher severity or exploitation evidence emerges.

Technical view

The fix cancels a timer in clone_dtr() to address a use-after-free when dm_resume() and dm_destroy() run concurrently in dm-clone. The CVE record lists Linux kernel as affected and references stable kernel commits. No CWE, CVSS vector, exploitability details, or attacker prerequisites are provided in the source bundle.

Likely exposure

Exposure is most relevant to systems running Linux kernels with the dm-clone target available or in use. The source bundle lists affected Linux kernel versions and stable fixes, but does not provide distribution-specific package mappings. Validate against your vendor kernel builds, not only upstream version numbers.

Exploitation context

No active exploitation is indicated. The CVE is not in KEV, and the provided sources do not describe public exploitation, proof-of-concept activity, or remote attack paths. The issue appears concurrency-related inside the kernel device-mapper clone code.

Researcher notes

The public record is sparse. Key evidence is the upstream fix description: dm-clone has a UAF when dm_resume() and dm_destroy() are concurrent, resolved by canceling a timer in clone_dtr(). Further impact analysis requires vendor advisories or kernel commit review beyond the provided metadata.

Mitigation direction

  • Check your Linux distribution or appliance vendor advisory for CVE-2022-50843 guidance.
  • Prioritize kernel updates that include the referenced upstream stable fixes.
  • Assess whether dm-clone is enabled or used on affected systems.
  • Apply standard kernel maintenance windows for exposed production Linux hosts.
  • If immediate patching is unavailable, monitor vendor guidance for supported mitigations.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded systems.
  • Identify systems using device-mapper clone functionality.
  • Confirm whether vendor kernel packages include the referenced stable commits.
  • Review vulnerability scanner results against vendor advisories, not upstream versions alone.
  • Document exceptions where dm-clone is absent or the vendor marks the build unaffected.
Prepared
Confidence
medium
Sources
8

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-2022-50843 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
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7431b7835f554f8608b415a02cf3c3f086309e02, 7431b7835f554f8608b415a02cf3c3f086309e02, 7431b7835f554f8608b415a02cf3c3f086309e02, 7431b7835f554f8608b415a02cf3c3f086309e02, 7431b7835f554f8608b415a02cf3c3f086309e02, 7431b7835f554f8608b415a02cf3c3f086309e02unaffected
LinuxLinux5.4, 0, 5.4.229, 5.10.163, 5.15.87, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

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