CVE-2026-45914

HIGH EPSS 2.6%
Published May 27, 20261mo ago · Modified Jun 24, 20265d ago
7.8 CVSS 3.1
High
Find Similar
Published May 27, 2026 1mo ago
Last Modified Jun 24, 2026 5d ago

Description

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 Details

Base Score
7.8
Exploitability
1.8
Impact
5.9
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality High
Integrity High
Availability High

Threat Intelligence

EPSS Exploit Probability
2.6% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-416 Use After Free Memory Safety

Affected Products 14

VendorProductVersionRange
linuxlinux_kernel*≥5.10.248  –  <5.10.252
linuxlinux_kernel*≥6.1.160  –  <6.1.165
linuxlinux_kernel*≥6.6.120  –  <6.6.128
linuxlinux_kernel*≥6.12.64  –  <6.12.75
linuxlinux_kernel*≥6.18.3  –  <6.18.14
linuxlinux_kernel*≥6.19.1  –  <6.19.4
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any
linuxlinux_kernel6.19any

References 7

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

Remediation

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