Kernel memory corruption via stale input-device cleanup
Published May 21, 2024 · Updated May 11, 2026
Use-after-free in the Linux kernel ibmasm driver allows local users to corrupt kernel memory after device initialization fails. ibmasm_init_one frees mouse and keyboard input devices on one error path, then passes their stale pointers to ibmasm_free_remote_input_dev for unregistration on a second path. Reachability requires the IBM ASM driver and a remote-input initialization failure; resulting memory corruption can compromise or interrupt the host.
Summary
What happened
Use-after-free in the Linux kernel ibmasm driver allows local users to corrupt kernel memory after device initialization fails. ibmasm_init_one frees mouse and keyboard input devices on one error path, then passes their stale pointers to ibmasm_free_remote_input_dev for unregistration on a second path. Reachability requires the IBM ASM driver and a remote-input initialization failure; resulting memory corruption can compromise or interrupt the host.
The record
- CVE
- CVE-2021-47334
- Published
- May 21, 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
- May 21, 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=2.6.16
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <1512e7dc5eb08b7d92a12e2bfcd9cb8c4a1ec069
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <29ba8e2ba89ee2862a26d91204dd5fe77ceee25a
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <38660031e80eaa6cc9370b031c180612f414b00d
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <481a76d4749ee3a27f902ba213fdcbb4bb39720e
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <5b06ca113bf197aab2ab61288f42506e0049fbab
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <7272b591c4cb9327c43443f67b8fbae7657dd9ae
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <a7268e8a227d5a4f0bd1584f556246b0224ab274
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <b9c87ce3bc6331f82811a8cf8e930423c22523a3
- Affected versionversion=736ce43295682d060f2b93624b4a339f9af6aab1 <ef1067d2baa847d53c9988510d99fb494de4d12c
What conditions does exploitation require?
What is affected?
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