High 7.8Published May 27, 2026

CVE-2026-45914Revert "hwmon: (ibmpex) fix use-after-free in high/low store"

Updated under an hour ago (Oct 27, 2026, 7:50 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

In the Linux kernel, the following vulnerability has been resolved: Revert "hwmon: (ibmpex) fix use-after-free in high/low store" This reverts commit 6946c726c3f4c36f0f049e6f97e88c510b15f65d. Jean Delvare points out that the patch does not completely fix the reported problem, that it in fact introduces a (new) race condition, and that it may actually not be needed in the first place. Various AI reviews agree. Specific and relevant AI feedback: " This reordering sets the driver data to NULL before removing the sensor attributes in the loop below. ibmpex_show_sensor() retrieves this driver data via dev_get_drvdata() but does not check if it is NULL before dereferencing it to access data->sensors[]. If a userspace process reads a sensor file (like temp1_input) while this delete function is running, could it race with the dev_set_drvdata(..., NULL) call here and crash in ibmpex_show_sensor()? Would it be safer to keep the original order where device_remove_file() is called before clearing the driver data? device_remove_file() should wait for any active sysfs callbacks to complete, which might already prevent the use-after-free this patch intends to fix. " Revert the offending patch. If it can be shown that the originally reported alleged race condition does indeed exist, it can always be re-introduced with a complete fix.

CVSS: 7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Undergoing Analysis
Record last updated: May 27, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from 3ce9b7ae9d4d148672b35147aaf7987a4f82bb94 before 05112ba67c824ab416cd54307c0b50aba9f0047a; from 533ead425f8109b02fecc7e72d612b8898ec347a before efd68429f23fb4015b0ebc2392334059e06fad18; from fa37adcf1d564ef58b9dfb01b6c36d35c5294bad before f448acd86835a650f9ea83460b9ca347d3aafba5; from 68d62e5bebbd118b763e8bb210d5cf2198ef450c before 914b47c9b824d3d74f31c764163edf93302100b1; from 5aa2139201667c1f644601e4529c4acd6bf8db5a before 14a38784e09aebc21207dc32fffa05247fc3dd64; 6946c726c3f4c36f0f049e6f97e88c510b15f65d builds before 894d9c7aab68fd0c70c78b1d03c8fa589fb0f67d; 6946c726c3f4c36f0f049e6f97e88c510b15f65d builds before 8bde3e395a85017f12af2b0ba5c3684f5af9c006; from 5.10.248 before 5.10.252; and 4 more ranges	CNA record
linux linux_kernel linux:linux_kernel	from 5.10.248 before 5.10.252; from 6.1.160 before 6.1.165; from 6.6.120 before 6.6.128; from 6.12.64 before 6.12.75; from 6.18.3 before 6.18.14; from 6.19.1 before 6.19.4; 6.19; 6.19; and 6 more ranges	NVD

References

References

https://git.kernel.org/stable/c/05112ba67c824ab416cd54307c0b50aba9f0047a	patch
https://git.kernel.org/stable/c/efd68429f23fb4015b0ebc2392334059e06fad18	patch
https://git.kernel.org/stable/c/f448acd86835a650f9ea83460b9ca347d3aafba5	patch
https://git.kernel.org/stable/c/914b47c9b824d3d74f31c764163edf93302100b1	patch
https://git.kernel.org/stable/c/14a38784e09aebc21207dc32fffa05247fc3dd64	patch
https://git.kernel.org/stable/c/894d9c7aab68fd0c70c78b1d03c8fa589fb0f67d	patch
https://git.kernel.org/stable/c/8bde3e395a85017f12af2b0ba5c3684f5af9c006	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.