Skip to main content
← All vulnerabilities
CVE-2026-98200

hwmon: (hp-wmi-sensors) Fix use-after-free in fungible_show()

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.6.158, 6.12.112, 6.18.54, 7.2.8
None on Exploit-DB, Metasploit or GitHub

Summary

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().

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 23902f98f8d4811ab84dde6419569a5b374f8122 · fixed in b6b2a638aa36c441b2c8d0b6bd8ed2bb9701e795; From 23902f98f8d4811ab84dde6419569a5b374f8122 · fixed in f59ecfd2c58bace39538f3fff7f43788b3fdb539; From 23902f98f8d4811ab84dde6419569a5b374f8122 · fixed in 72c85149794a1ccf8d718ffed1521106b5d31968; From 23902f98f8d4811ab84dde6419569a5b374f8122 · fixed in 9c1e65bc79ff104914b11e6ad972139296ec86fe; From 23902f98f8d4811ab84dde6419569a5b374f8122 · fixed in e6cb0b4d4ecb8e71fd2200d907ab2e9663356f69

  • Linux Linux

    6.5

  • KernelLinux

    From 6.5.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.54; From 6.19.0 · fixed in 7.2.8

References 5

git.kernel.org