Kernel crash via unchecked event waiter allocation
Published Feb 26, 2025 · Updated May 11, 2026
Null-pointer dereference in Linux kernel AMD KFD event handling allows local users to crash the kernel when event-waiter allocation fails. The event creation path in drivers/gpu/drm/amd/amdkfd/kfd_events.c dereferences event_waiters[i].wait without checking whether kmalloc_array() returned null. A low-privileged local user must reach AMD KFD event creation under memory pressure; the documented consequence is a kernel crash, not data access or modification.
Summary
What happened
Null-pointer dereference in Linux kernel AMD KFD event handling allows local users to crash the kernel when event-waiter allocation fails. The event creation path in drivers/gpu/drm/amd/amdkfd/kfd_events.c dereferences event_waiters[i].wait without checking whether kmalloc_array() returned null. A low-privileged local user must reach AMD KFD event creation under memory pressure; the documented consequence is a kernel crash, not data access or modification.
The record
- CVE
- CVE-2022-49055
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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=4.2
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <0a692c625e373fef692ffbc7fc41f8a025f01cb7
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <1d7a5aae884ca727d41c7ed15d4c82fdb67c040c
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <32cf90a521dcc0f136db7ee5ba32bfe5f79e460e
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <40bf32dbfef866c83a3e74800b81d79e52b6d20b
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <94869bb0de69a812f70231b0eb480bb2f7ae73a6
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <c7a268b33882d5feaafd29c1734456f41ba41396
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <ebbb7bb9e80305820dc2328a371c1b35679f2667
- Affected versionversion=f3a398183f7b9ef78f6b71ee9f7641e046403bcb <f2658d5966bcee8c3eb487875f459756d4f7cdfc
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.
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