Local kernel crash via dangling ibmpex list entry
Published Oct 21, 2024 · Updated Aug 5, 2026
Use-after-free in the ibmpex hwmon driver in Linux allows local users to crash the kernel after a failed BMC sensor probe. When ibmpex_find_sensors() fails, ibmpex_register_bmc() frees its data object without removing data->list from driver_data.bmc_data, so later list traversal dereferences freed memory. Reachability requires an affected IBM System X host using the ibmpex driver through a local IPMI BMC interface; kernel memory reuse can expose or alter memory and interrupt the host.
Summary
What happened
Use-after-free in the ibmpex hwmon driver in Linux allows local users to crash the kernel after a failed BMC sensor probe. When ibmpex_find_sensors() fails, ibmpex_register_bmc() frees its data object without removing data->list from driver_data.bmc_data, so later list traversal dereferences freed memory. Reachability requires an affected IBM System X host using the ibmpex driver through a local IPMI BMC interface; kernel memory reuse can expose or alter memory and interrupt the host.
The record
- CVE
- CVE-2022-49029
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.24
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <24b9633f7db7f4809be7053df1d2e117e7c2de10
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <45f6e81863747c0d7bc6a95ec51129900e71467a
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <798198273bf86673b970b51acdb35e57f42b3fcb
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <7b2b67fe1339389e0bf3c37c7a677a004ac0e4e3
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <90907cd4d11351ff76c9a447bcb5db0e264c47cd
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <e2a87785aab0dac190ac89be6a9ba955e2c634f2
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <e65cfd1f9cd27d9c27ee5cb88128a9f79f25d863
- Affected versionversion=57c7c3a0fdea95eddcaeba31e7ca7dfc917682ab <f2a13196ad41c6c2ab058279dffe6c97292e753a
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