hwmon: (hp-wmi-sensors) Fix use-after-free in fungible_show()
Summary
| CVE | CVE-2026-98200 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-06 09:18:05 UTC |
| Updated | 2026-10-06 09:18:05 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
hwmon: (hp-wmi-sensors) Fix use-after-free in fungible_show()
nsensor->current_state is dynamically replaced as the sensor's state
changes. update_numeric_sensor_from_wobj() does this by freeing the
old string and installing a new one:
if (strcmp(trimmed, nsensor->current_state)) {
new_string = hp_wmi_strdup(dev, trimmed);
if (new_string) {
devm_kfree(dev, nsensor->current_state);
nsensor->current_state = new_string;
}
}
This function is only ever called from hp_wmi_update_info() while
state->lock is held, so the free-and-replace itself is properly
serialized against concurrent updates.
fungible_show(), however, reads the same pointer after the lock has
already been dropped:
err = hp_wmi_update_info(state, info);
if (err)
return err;
switch (prop) {
...
case HP_WMI_PROPERTY_CURRENT_STATE:
seq_printf(seqf, "%s\n", nsensor->current_state);
break;
hp_wmi_update_info() takes state->lock internally and releases it
before returning, so by the time fungible_show() dereferences
nsensor->current_state in seq_printf(), no lock is held. Two
processes reading a sensor's current_state debugfs entry at
overlapping times (or one reading it while another read of the same
sensor triggers a refresh) can race: one thread's seq_printf() can
be part-way through printing the string at the moment another
thread's call into update_numeric_sensor_from_wobj() frees it with
devm_kfree() and installs a new pointer, causing a use-after-free
read.
Take state->lock around the read in fungible_show() as well, so it
can never run concurrently with the free-and-replace in
update_numeric_sensor_from_wobj(). |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 23902f98f8d4811ab84dde6419569a5b374f8122 b6b2a638aa36c441b2c8d0b6bd8ed2bb9701e795 git |
Not specified |
| CNA |
Linux |
Linux |
affected 23902f98f8d4811ab84dde6419569a5b374f8122 f59ecfd2c58bace39538f3fff7f43788b3fdb539 git |
Not specified |
| CNA |
Linux |
Linux |
affected 23902f98f8d4811ab84dde6419569a5b374f8122 72c85149794a1ccf8d718ffed1521106b5d31968 git |
Not specified |
| CNA |
Linux |
Linux |
affected 23902f98f8d4811ab84dde6419569a5b374f8122 9c1e65bc79ff104914b11e6ad972139296ec86fe git |
Not specified |
| CNA |
Linux |
Linux |
affected 23902f98f8d4811ab84dde6419569a5b374f8122 e6cb0b4d4ecb8e71fd2200d907ab2e9663356f69 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.5 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.5 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.158 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.112 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.54 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.8 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc4 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/e6cb0b4d4ecb8e71fd2200d907ab2e9663356f69 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b6b2a638aa36c441b2c8d0b6bd8ed2bb9701e795 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/72c85149794a1ccf8d718ffed1521106b5d31968 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9c1e65bc79ff104914b11e6ad972139296ec86fe |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f59ecfd2c58bace39538f3fff7f43788b3fdb539 |
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.