high CVSS 7.8

CVE-2022-49029·Kernel vulnerability

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().

Severity
high
Software
Kernel
Fixed in
6.0.12
Published
2024-10-21

Affected versions

From: 5.16

Until: 6.0.12

Fixed in: 6.0.12

How to fix this CVE

Update your Linux kernel to version 6.0.12 or later to resolve a use-after-free vulnerability in the IBM PowerPC Exposed-Registers (IBMPEX) hardware monitoring driver. This flaw could lead to kernel crashes or potential privilege escalation if the IBMPEX registration process fails during sensor enumeration. Apply kernel updates through your distribution's package manager and reboot to activate the patched version.

sudo dnf update kernel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your current kernel version with: uname -r — compare against the affected range (5.16 to 6.0.11)
  2. Step 2: Verify if IBMPEX driver is loaded by running: lsmod | grep ibmpex — if no output, this driver is not active on your system
  3. Step 3: Search system logs for IBMPEX-related errors with: sudo dmesg | grep -i ibmpex or sudo journalctl -u kernel | grep -i ibmpex — look for registration failures or UAF warnings
  4. Step 4: After patching to 6.0.12 or later, confirm with: uname -r — ensure the new kernel version is running

FAQ

What is CVE-2022-49029?

CVE-2022-49029 is a use-after-free vulnerability in the Linux kernel's IBMPEX hardware monitoring driver where a freed data structure remains referenced in a global list, potentially causing kernel panics or privilege escalation if sensor registration fails.

Is CVE-2022-49029 being actively exploited?

No, CVE-2022-49029 is not listed on the CISA KEV catalog and has no public exploits available, though the vulnerability is still critical and should be patched promptly.

What versions of Kernel are affected by CVE-2022-49029?

Linux kernel versions 5.16 through 6.0.11 are vulnerable; kernel 6.0.12 and later versions contain the fix.

How do I check if my server is vulnerable to CVE-2022-49029?

Run uname -r to display your kernel version; if the output falls between 5.16 and 6.0.11, your system is vulnerable (affected systems with IBMPEX loaded are at highest risk).

Does Defensia detect CVE-2022-49029?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2022-49029 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2024-39462CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: clk: bcm: dvp: Assign ->num before accessing ->hws Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with __counted_by") annotated the hws member of 'struct clk_hw_onecell_data' with __counted_by, which informs the bounds sanitizer about the number of elements in hws, so that it can warn when hws is accessed out of bounds. As noted in that change, the __counted_by member must be initialized with the number of elements before the first array access happens, otherwise there will be a warning from each access prior to the initialization because the number of elements is zero. This occurs in clk_dvp_probe() due to ->num being assigned after ->hws has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/bcm/clk-bcm2711-dvp.c:59:2 index 0 is out of range for type 'struct clk_hw *[] __counted_by(num)' (aka 'struct clk_hw *[]') Move the ->num initialization to before the first access of ->hws, which clears up the warning.
CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2021-47378CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: nvme-rdma: destroy cm id before destroy qp to avoid use after free We should always destroy cm_id before destroy qp to avoid to get cma event after qp was destroyed, which may lead to use after free. In RDMA connection establishment error flow, don't destroy qp in cm event handler.Just report cm_error to upper level, qp will be destroy in nvme_rdma_alloc_queue() after destroy cm id.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49029. Free for 1 server.

Get started free