Kernel crash via unchecked host registration failure
Published Dec 24, 2025 · Updated Dec 24, 2025
Resource-management error in affected Linux kernel releases allows local users to crash the kernel when a failed mxcmmc host is removed. The mxcmmc probe path ignores an error from mmc_add_host(), leaking the mmc_alloc_host() allocation and leaving an unregistered host for the remove path to delete. Reachability requires the mxcmmc driver, a failed host-registration call, and subsequent device removal; the documented consequence is a service-interrupting kernel crash.
Summary
What happened
Resource-management error in affected Linux kernel releases allows local users to crash the kernel when a failed mxcmmc host is removed. The mxcmmc probe path ignores an error from mmc_add_host(), leaking the mmc_alloc_host() allocation and leaving an unregistered host for the remove path to delete. Reachability requires the mxcmmc driver, a failed host-registration call, and subsequent device removal; the documented consequence is a service-interrupting kernel crash.
The record
- CVE
- CVE-2022-50769
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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=d96be879ff469759af6d7fcebdb66237c18da6f8 <1cf0c1e58738b97e2de207846105b6a5d46622ee
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <2d496050ded83b13b16f05e1fc0329b0210d2493
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <32eb502c972dfc34413c9147418b3d94d870c2b8
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <3904eb97bb78fdca3e16d30a38ce5697b9686110
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <5f35c038c9f4d258b3cf77885a2730f1417d63e7
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <b8bdb3fd13d5cd1e86d22fd3f803a742fd88af89
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <cde600af7b413c9fe03e85c58c4279df90e91d13
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <d2ead18bc7cc166220cab5a744a05c5b69431a12
- Affected versionversion=d96be879ff469759af6d7fcebdb66237c18da6f8 <d37474ab9a79149075f0823315c6d45dd983a78c
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