Revert "hwmon: (ibmpex) fix use-after-free in high/low store"
Summary
| CVE | CVE-2026-45914 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-27 14:17:06 UTC |
| Updated | 2026-05-27 14:48:03 UTC |
| 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. |
Risk And Classification
EPSS: 0.000240000 probability, percentile 0.073320000 (date 2026-06-01)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 3ce9b7ae9d4d148672b35147aaf7987a4f82bb94 05112ba67c824ab416cd54307c0b50aba9f0047a git | Not specified |
| CNA | Linux | Linux | affected 533ead425f8109b02fecc7e72d612b8898ec347a efd68429f23fb4015b0ebc2392334059e06fad18 git | Not specified |
| CNA | Linux | Linux | affected fa37adcf1d564ef58b9dfb01b6c36d35c5294bad f448acd86835a650f9ea83460b9ca347d3aafba5 git | Not specified |
| CNA | Linux | Linux | affected 68d62e5bebbd118b763e8bb210d5cf2198ef450c 914b47c9b824d3d74f31c764163edf93302100b1 git | Not specified |
| CNA | Linux | Linux | affected 5aa2139201667c1f644601e4529c4acd6bf8db5a 14a38784e09aebc21207dc32fffa05247fc3dd64 git | Not specified |
| CNA | Linux | Linux | affected 6946c726c3f4c36f0f049e6f97e88c510b15f65d 894d9c7aab68fd0c70c78b1d03c8fa589fb0f67d git | Not specified |
| CNA | Linux | Linux | affected 6946c726c3f4c36f0f049e6f97e88c510b15f65d 8bde3e395a85017f12af2b0ba5c3684f5af9c006 git | Not specified |
| CNA | Linux | Linux | affected 5.10.248 5.10.252 semver | Not specified |
| CNA | Linux | Linux | affected 6.1.160 6.1.165 semver | Not specified |
| CNA | Linux | Linux | affected 6.6.120 6.6.128 semver | Not specified |
| CNA | Linux | Linux | affected 6.12.64 6.12.75 semver | Not specified |
| CNA | Linux | Linux | affected 6.18.3 6.18.14 semver | Not specified |
| CNA | Linux | Linux | affected 6.19 | Not specified |
| CNA | Linux | Linux | unaffected 6.19 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.252 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.165 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.128 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.75 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.14 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.4 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/894d9c7aab68fd0c70c78b1d03c8fa589fb0f67d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/914b47c9b824d3d74f31c764163edf93302100b1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/14a38784e09aebc21207dc32fffa05247fc3dd64 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/05112ba67c824ab416cd54307c0b50aba9f0047a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/efd68429f23fb4015b0ebc2392334059e06fad18 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8bde3e395a85017f12af2b0ba5c3684f5af9c006 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f448acd86835a650f9ea83460b9ca347d3aafba5 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.