CVE-2022-49029: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails
Smatch report warning as follows:
drivers/hwmon/ibmpex.c:509 ibmpex_register_bmc() warn:
'&data->list' not removed from list
If ibmpex_find_sensors() fails in ibmpex_register_bmc(), data will
be freed, but data->list will not be removed from driver_data.bmc_data,
then list traversal may cause UAF.
Fix by removeing it from driver_data.bmc_data before free().
Security readout for executives and security teams
Plain-English summary
CVE-2022-49029 is a Linux kernel memory-safety flaw in the ibmpex hardware monitoring driver. If sensor discovery fails during BMC registration, the kernel may later reference freed memory. The public sources do not provide a CVSS score, exploitation evidence, or impact beyond the use-after-free condition.
Executive priority
Treat this as a targeted kernel maintenance issue, not an emergency based on current evidence. Prioritize normal patch cycles, with faster action for Linux hosts using ibmpex or BMC hardware monitoring in production.
Technical view
In drivers/hwmon/ibmpex.c, ibmpex_register_bmc() can free data after ibmpex_find_sensors() fails without removing data->list from driver_data.bmc_data. Later list traversal can trigger a use-after-free. Stable kernel commits fix this by removing the list entry before freeing the object.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions where the ibmpex hwmon driver is present and the BMC sensor registration path is exercised. The bundle lists Linux as affected, with versions including 2.6.24 through several stable series before their referenced fixes.
Exploitation context
The source bundle states KEV is false and provides no cited evidence of active exploitation, public exploit code, or real-world abuse. The available record supports a kernel use-after-free condition but does not establish practical exploitability or attacker prerequisites.
Researcher notes
The strongest evidence is the kernel commit narrative: a Smatch warning found a stale list entry after an error path. Missing data includes CVSS, CWE mapping, exploit prerequisites, and confirmed affected distribution packages. Avoid assuming broader impact beyond Linux ibmpex driver contexts.
Mitigation direction
Update to a vendor kernel containing the referenced stable fix.
Prioritize systems using the ibmpex hwmon driver or BMC monitoring path.
Check Linux distribution advisories for backported fixes.
If patch timing is unclear, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory kernel versions against the affected versions in the CVE record.
Review kernel configuration or module inventory for ibmpex hwmon support.
Confirm installed kernels include the applicable stable commit or vendor backport.
Document whether affected systems use BMC sensor monitoring workflows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49029 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.