Kernel invalid access via freed MMC host
Published Feb 25, 2024 · Updated May 11, 2026
Use-after-free in the Moxart MMC host driver allows local users to trigger an invalid kernel-memory access during device removal. moxart_remove() frees the MMC host and then derives a base-register access through the released host pointer instead of preserving the register first. Reachability requires the affected driver and its device-removal path; public sources identify no reliable trigger or demonstrated consequence beyond the invalid access.
Summary
What happened
Use-after-free in the Moxart MMC host driver allows local users to trigger an invalid kernel-memory access during device removal. moxart_remove() frees the MMC host and then derives a base-register access through the released host pointer instead of preserving the register first. Reachability requires the affected driver and its device-removal path; public sources identify no reliable trigger or demonstrated consequence beyond the invalid access.
The record
- CVE
- CVE-2022-48626
- Published
- Feb 25, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 2024CVE 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=1b66e94e6b9995323190f31c51d8e1a6f516627e <3a0a7ec5574b510b067cfc734b8bdb6564b31d4e
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <7f901d53f120d1921f84f7b9b118e87e94b403c5
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <9c25d5ff1856b91bd4365e813f566cb59aaa9552
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <af0e6c49438b1596e4be8a267d218a0c88a42323
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <bd2db32e7c3e35bd4d9b8bbff689434a50893546
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <be93028d306dac9f5b59ebebd9ec7abcfc69c156
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <e6f580d0b3349646d4ee1ce0057eb273e8fb7e2e
- Affected versionversion=1b66e94e6b9995323190f31c51d8e1a6f516627e <f5dc193167591e88797262ec78515a0cbe79ff5f
- Affected versionversion=3.16
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.
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