LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50858: mmc: alcor: fix return value check of mmc_add_host()

In the Linux kernel, the following vulnerability has been resolved: mmc: alcor: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, the memory that allocated in mmc_alloc_host() will be leaked and it will lead a kernel crash because of deleting not added device in the remove path. So fix this by checking the return value and calling mmc_free_host() in the error path.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50858 is a Linux kernel bug in the Alcor MMC driver. If adding an MMC host fails, the driver may leak memory and later crash the kernel during device removal. Business impact is primarily availability, not confirmed data theft. Public sources do not provide a CVSS score or evidence of active exploitation.

Executive priority

Treat as a routine-to-priority Linux availability fix. It is not supported by current sources as an actively exploited emergency, but kernel crashes can affect uptime on exposed systems. Patch through normal kernel maintenance, prioritizing systems using the relevant hardware or driver.

Technical view

The bug is an unchecked return value from mmc_add_host() in the Linux kernel Alcor MMC path. On failure, memory allocated by mmc_alloc_host() was not freed, and later remove handling could delete a device that was never added, causing a kernel crash. Stable kernel commits add error handling and mmc_free_host() on the failure path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the relevant Alcor MMC driver path reachable. The source lists Linux as affected across several stable version lines, but does not name distributions, devices, or default configurations.

Exploitation context

No cited source states active exploitation, public exploit availability, or KEV listing. The described failure depends on an mmc_add_host() error condition and subsequent remove path. Sources support an availability-risk interpretation, but do not establish remote exploitability or privilege requirements.

Researcher notes

The public record is sparse: no CVSS, CWE, exploit status, or distribution advisories are included. Analysis should focus on affected kernel lineage, whether the Alcor MMC driver is built and reachable, and whether stable-tree fixes are present. Avoid assuming broader impact beyond the documented crash condition.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable Linux fixes.
  • If self-maintaining kernels, backport the relevant stable commit for your kernel branch.
  • Prioritize systems where Alcor MMC hardware or driver support is enabled.
  • If no update is available, consult your Linux vendor for supported guidance.

Validation and detection

  • Inventory Linux kernel versions against the affected version information in the CVE record.
  • Verify whether the Alcor MMC driver is present or enabled on relevant systems.
  • Confirm the fix commit or vendor backport exists in deployed kernel sources.
  • Review kernel crash logs for MMC or Alcor-related remove-path crashes.
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-50858 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
LinuxLinuxc5413ad815a675b5c98a002353d8e96b44b164e9, c5413ad815a675b5c98a002353d8e96b44b164e9, c5413ad815a675b5c98a002353d8e96b44b164e9, c5413ad815a675b5c98a002353d8e96b44b164e9, c5413ad815a675b5c98a002353d8e96b44b164e9, c5413ad815a675b5c98a002353d8e96b44b164e9unaffected
LinuxLinux5.0, 0, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 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.