Kernel crash via unchecked MMC host failure
Published Dec 9, 2025 · Updated May 11, 2026
Improper error handling in the Linux kernel OMAP MMC host driver allows local users to crash the kernel during device removal. The omap_hsmmc probe path ignores an mmc_add_host() failure, leaks the mmc_alloc_host() allocation, and later passes an unregistered device to mmc_remove_host(), causing a null-pointer dereference in device_del(). Reachability requires local access and an OMAP MMC device configuration in which host registration fails before the driver's remove path runs.
Summary
What happened
Improper error handling in the Linux kernel OMAP MMC host driver allows local users to crash the kernel during device removal. The omap_hsmmc probe path ignores an mmc_add_host() failure, leaks the mmc_alloc_host() allocation, and later passes an unregistered device to mmc_remove_host(), causing a null-pointer dereference in device_del(). Reachability requires local access and an OMAP MMC device configuration in which host registration fails before the driver's remove path runs.
The record
- CVE
- CVE-2022-50670
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.29
- Affected versionversion=a45c6cb816474cefe56059fce422a9bdcd77e0dc <4e1dc24bcfc8257f24c0663badec7e4f3ae80558
- Affected versionversion=a45c6cb816474cefe56059fce422a9bdcd77e0dc <62005dfcc396424db3337a1dc3ab49623537f5e5
- Affected versionversion=a45c6cb816474cefe56059fce422a9bdcd77e0dc <a525cad241c339ca00bf7ebf03c5180f2a9b767c
- Affected versionversion=a45c6cb816474cefe56059fce422a9bdcd77e0dc <a5f8a4583280a76e50329b910e91ef1dea1e6c79
- Affected versionversion=a45c6cb816474cefe56059fce422a9bdcd77e0dc <f153c9e15f8961bdf38707853e15b42ea7c691d9
- Affected versionversion=a45c6cb816474cefe56059fce422a9bdcd77e0dc <fb3d596267a98813a7a8206097d8d46c98505a0d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo