Answer in brief
CVE-2026-90311 records a Unknown severity vulnerability in thermal: hwmon: Remove hwmon class device along with its parent. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <2b57e24d34b2dfc43c81942bb359d6315bf302fb | 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4, 2b57e24d34b2dfc43c81942bb359d6315bf302fb |
| Linux/Linuxgeneric | 4.19 | Not reported |
| Linux/Linuxgeneric | >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <9b405b3e7e131ee85dd78b9cc951b41f0828a333 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <2b57e24d34b2dfc43c81942bb359d6315bf302fb | 9b405b3e7e131ee85dd78b9cc951b41f0828a333, 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4, 2b57e24d34b2dfc43c81942bb359d6315bf302fb |
| Linux/Linuxgeneric | >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <df002834cfd880b800fa607135e4bb2e403ce187 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <23094544b8e8c43909fd61ca8866ecfe38093ae8 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <9b405b3e7e131ee85dd78b9cc951b41f0828a333 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <2b57e24d34b2dfc43c81942bb359d6315bf302fb | df002834cfd880b800fa607135e4bb2e403ce187, 23094544b8e8c43909fd61ca8866ecfe38093ae8, 9b405b3e7e131ee85dd78b9cc951b41f0828a333, 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4, 2b57e24d34b2dfc43c81942bb359d6315bf302fb |
| Linux/Linuxgeneric | >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <e67dad2cff9e4fedce69e752d515ef651d745a90 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <df002834cfd880b800fa607135e4bb2e403ce187 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <23094544b8e8c43909fd61ca8866ecfe38093ae8 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <9b405b3e7e131ee85dd78b9cc951b41f0828a333 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 || >=f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 <2b57e24d34b2dfc43c81942bb359d6315bf302fb | e67dad2cff9e4fedce69e752d515ef651d745a90, df002834cfd880b800fa607135e4bb2e403ce187, 23094544b8e8c43909fd61ca8866ecfe38093ae8, 9b405b3e7e131ee85dd78b9cc951b41f0828a333, 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4, 2b57e24d34b2dfc43c81942bb359d6315bf302fb |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In the Linux kernel, the following vulnerability has been resolved: thermal: hwmon: Remove hwmon class device along with its parent The current code creates one hwmon device per thermal zone type and that device is registered under the first thermal zone of the given type. That turns out to be problematic when the thermal zone holding the hwmon device is removed. For example, say that there are two ACPI thermal zones on a system /sys/devices/virtual/thermal/thermal_zone0/ /sys/devices/virtual/thermal/thermal_zone1/ The current code registers a hwmon class device for thermal_zone0 only: /sys/devices/virtual/thermal/thermal_zone0/hwmon0/ because the type is "acpitz" for both of them, but it adds a sysfs attribute that belongs to thermal_zone1 under it: /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp2_input There is also /sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input which belongs to thermal_zone0. When thermal_zone0 is removed, say because the ACPI thermal driver is unbound from the underlying platform device, thermal_remove_hwmon_sysfs() skips the removal of hwmon0 because of the temp2_input attribute belonging to thermal_zone1 which effectively prevents thermal_zone0 removal from making progress. Address this by making thermal_remove_hwmon_sysfs() remove the entire hwmon class device interface for the given thermal zone type when the thermal zone device holding it is removed. To prevent races with thermal_add_hwmon_sysfs() that may interfere with this, carry out the entire addition and removal of hwmon sysfs interfaces for thermal zones under thermal_hwmon_list_lock. Also adjust the layout of the labels in thermal_add_hwmon_sysfs() to the current kernel coding style to align with the new "unlock" label.
Quoted source text, attributed separately from HOL analysis.