Kernel crash via unchecked host-registration failure
Published Dec 9, 2025 · Updated May 11, 2026
Improper error handling in the atmel-mci driver in Linux allows attackers to crash the kernel via a failed host-registration path. The probe path ignores an error returned by mmc_add_host(), leaks the host allocated by mmc_alloc_host(), and leaves removal to call device_del() for a device that was never registered. The crash requires host registration to fail and the affected device's remove path to run; public records do not identify an attacker-controlled trigger or required privileges.
Summary
What happened
Improper error handling in the atmel-mci driver in Linux allows attackers to crash the kernel via a failed host-registration path. The probe path ignores an error returned by mmc_add_host(), leaks the host allocated by mmc_alloc_host(), and leaves removal to call device_del() for a device that was never registered. The crash requires host registration to fail and the affected device's remove path to run; public records do not identify an attacker-controlled trigger or required privileges.
The record
- CVE
- CVE-2022-50653
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
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.27
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <00ac0f5f95920f003cd6ece53cdc759549b69118
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <1925472dec31ec061d57412b3a65a056ea24f340
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <6bb26abb92f25e582a0976091a10b539fe3796db
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <85946ceb0fac20ab39cdb85333086daf0291a553
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <99a6cdfa2cf05028b52f6d8ee85ccc5f8b71b4a2
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <9e6e8c43726673ca2abcaac87640b9215fd72f4c
- Affected versionversion=7d2be0749a59096a334c94dc48f43294193cb8ed <cc8bb436f3c842a86b9082d97933582120d180e2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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