<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-09T19:46:14.935041+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-98200</id>
    <title>CVE-2026-98200 — hwmon: (hp-wmi-sensors) Fix use-after-free in fungible_show()</title>
    <updated>2026-10-09T19:46:14.950221+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>hwmon: (hp-wmi-sensors) Fix use-after-free in fungible_show()</p>
<p>nsensor-&gt;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:</p>
<p>if (strcmp(trimmed, nsensor-&gt;current_state)) {
		new_string = hp_wmi_strdup(dev, trimmed);
		if (new_string) {
			devm_kfree(dev, nsensor-&gt;current_state);
			nsensor-&gt;current_state = new_string;
		}
	}</p>
<p>This function is only ever called from hp_wmi_update_info() while
state-&gt;lock is held, so the free-and-replace itself is properly
serialized against concurrent updates.</p>
<p>fungible_show(), however, reads the same pointer after the lock has
already been dropped:</p>
<p>err = hp_wmi_update_info(state, info);
	if (err)
		return err;</p>
<p>switch (prop) {
	...
	case HP_WMI_PROPERTY_CURRENT_STATE:
		seq_printf(seqf, "%s\n", nsensor-&gt;current_state);
		break;</p>
<p>hp_wmi_update_info() takes state-&gt;lock internally and releases it
before returning, so by the time fungible_show() dereferences
nsensor-&gt;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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-98200"/>
  </entry>
</feed>
