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

Q: Who is exposed to this issue?

Systems running the Linux kernel with the hwmon ibmpex driver are relevant. Exploitation requires local access and low privileges; the described race involves userspace reading an ibmpex sensor sysfs file while the driver delete path runs.

Q: What does an attacker need to do to exploit the race?

A local low-privileged process would need to read a sensor attribute such as temp1_input concurrently with driver removal. The vulnerable ordering can set driver data to NULL before sensor attributes are removed, while ibmpex_show_sensor() dereferences that data without a NULL check.

Q: How can I determine whether a system has the problematic change?

Check the kernel source or applied stable commits for the referenced revert commits: 05112ba67c824ab416cd54307c0b50aba9f0047a, efd68429f23fb4015b0ebc2392334059e06fad18, or f448acd86835a650f9ea83460b9ca347d3aafba5. A kernel containing the revert removes the offending patch described by this issue.

Published May 27, 2026

Updated

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.

ibmpexshowsensor() retrieves this driver data via devgetdrvdata() but does not check if it is NULL before dereferencing it to access data->sensors[].

If a userspace process reads a sensor file (like temp1input) while this delete function is running, could it race with the devsetdrvdata(..., NULL) call here and crash in ibmpexshowsensor()?

Would it be safer to keep the original order where deviceremovefile() is called before clearing the driver data? deviceremovefile() 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.

Affected Software

160 affected componentsFixes available

Linux Linux kernel (hwmon: ibmpex)

Linux Linux kernel>=5.10.248<5.10.252

Linux Linux kernel>=6.1.160<6.1.165

Linux Linux kernel>=6.6.120<6.6.128

Linux Linux kernel>=6.12.64<6.12.75

Linux Linux kernel>=6.18.3<6.18.14

Linux Linux kernel>=6.19.1<6.19.4

Linux Linux kernel=6.19

Linux Linux kernel=6.19-rc2

Linux Linux kernel=6.19-rc3

Linux Linux kernel=6.19-rc4

Linux Linux kernel=6.19-rc5

Linux Linux kernel=6.19-rc6

Linux Linux kernel=6.19-rc7

Linux Linux kernel=6.19-rc8

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1060.63~22.04.1

6.8.0-1060.63~22.04.1

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1063.71~22.04.1

6.8.0-1063.71~22.04.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-azure-fde-6.8<6.8.0-1062.69~22.04.1

6.8.0-1062.69~22.04.1

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1063.69~22.04.1

6.8.0-1063.69~22.04.1

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-hwe-6.8<6.8.0-136.136~22.04.1

6.8.0-136.136~22.04.1

ubuntu/linux-ibm-6.8<6.8.0-1060.61~22.04.1

6.8.0-1060.61~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-134.134.1~22.04.1

6.8.0-134.134.1~22.04.1

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1058.61~22.04.1

6.8.0-1058.61~22.04.1

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1057.58~22.04.1

6.8.0-1057.58~22.04.1

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-134.134~22.04.1

6.8.0-134.134~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime-6.8<6.8.1-1055.56~22.04.1

6.8.1-1055.56~22.04.1

ubuntu/linux<6.8.0-134.134

6.8.0-134.134

ubuntu/linux-aws<6.8.0-1060.63

6.8.0-1060.63

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17*

ubuntu/linux-azure<6.8.0-1063.71

6.8.0-1063.71

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.17*

ubuntu/linux-azure-fde<6.8.0-1062.69

6.8.0-1062.69

ubuntu/linux-gcp<6.8.0-1063.69

6.8.0-1063.69

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gke<6.8.0-1058.64

6.8.0-1058.64

ubuntu/linux-gkeop<6.8.0-1045.48

6.8.0-1045.48

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-hwe-6.17*

ubuntu/linux-ibm<6.8.0-1060.61

6.8.0-1060.61

ubuntu/linux-lowlatency<6.8.0-134.134.1

6.8.0-134.134.1

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia<6.8.0-1058.61

6.8.0-1058.61

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17*

ubuntu/linux-nvidia-lowlatency<6.8.0-1058.61.1

6.8.0-1058.61.1

ubuntu/linux-nvidia-tegra<6.8.0-1029.30

6.8.0-1029.30

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17*

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1057.58

6.8.0-1057.58

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17*

ubuntu/linux-raspi<6.8.0-1060.64

6.8.0-1060.64

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-riscv-6.17*

ubuntu/linux-xilinx<6.8.0-1032.33

6.8.0-1032.33

ubuntu/linux-bluefield<6.8.0-1026.30

6.8.0-1026.30

ubuntu/linux-raspi-realtime<6.8.0-2049.50

6.8.0-2049.50

ubuntu/linux-realtime<6.8.1-1055.56

6.8.1-1055.56

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17*

ubuntu/linux-aws-fips<6.8.0-1060.63+fips1

6.8.0-1060.63+fips1

ubuntu/linux-azure-fips<6.8.0-1062.69+fips1

6.8.0-1062.69+fips1

ubuntu/linux-fips<6.8.0-134.134+fips1

6.8.0-134.134+fips1

ubuntu/linux-gcp-fips<6.8.0-1063.69+fips1

6.8.0-1063.69+fips1

ubuntu/linux*

ubuntu/linux-aws*

ubuntu/linux-azure*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp*

ubuntu/linux-oracle*

ubuntu/linux-raspi*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1060.63~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1063.71~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1062.69~22.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1063.69~22.04.1
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-136.136~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1060.61~22.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-134.134.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.61~22.04.1
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1057.58~22.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-134.134~22.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1055.56~22.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-134.134
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1060.63
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1063.71
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 6.8.0-1062.69
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1063.69
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.64
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1045.48
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1060.61
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-134.134.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.61
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.61.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1029.30
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1057.58
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1060.64
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1032.33
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 6.8.0-1026.30
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2049.50
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1055.56
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1060.63+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1062.69+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-134.134+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1063.69+fips1
Upgrade
Upgrade Linux kernel to a version that resolves this vulnerability.
Patch 6946c726c3f4c36f0f049e6f97e88c510b15f65d

Event History

May 27, 2026

CVE Published

via MITRE·12:17 PM

Data Sourced

via MITRE·12:17 PM

Description

Data Sourced

via OSV·02:17 PM

DescriptionSeverityAffected Software

Data Sourced

via NVD·02:17 PM

RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

Who is exposed to this issue?

Systems running the Linux kernel with the hwmon ibmpex driver are relevant. Exploitation requires local access and low privileges; the described race involves userspace reading an ibmpex sensor sysfs file while the driver delete path runs.

What does an attacker need to do to exploit the race?

A local low-privileged process would need to read a sensor attribute such as temp1_input concurrently with driver removal. The vulnerable ordering can set driver data to NULL before sensor attributes are removed, while ibmpex_show_sensor() dereferences that data without a NULL check.

How can I determine whether a system has the problematic change?

Check the kernel source or applied stable commits for the referenced revert commits: 05112ba67c824ab416cd54307c0b50aba9f0047a, efd68429f23fb4015b0ebc2392334059e06fad18, or f448acd86835a650f9ea83460b9ca347d3aafba5. A kernel containing the revert removes the offending patch described by this issue.

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

Affected Software

Remediation

Event History

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to do to exploit the race?

How can I determine whether a system has the problematic change?

Company

Resources

Contact