CVE-2026-90311: thermal: hwmon: Remove hwmon class device along with its parent
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 23094544b8e8c43909fd61ca8866ecfe38093ae8, 2b57e24d34b2dfc43c81942bb359d6315bf302fb, 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4.
Low priority for now. Upgrade to Linux Linux 23094544b8e8c43909fd61ca8866ecfe38093ae8, 2b57e24d34b2dfc43c81942bb359d6315bf302fb, 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.19affected
- f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 and later · before e67dad2cff9e4fedce69e752d515ef651d745a90affected · git
- f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 and later · before df002834cfd880b800fa607135e4bb2e403ce187affected · git
- f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 and later · before 23094544b8e8c43909fd61ca8866ecfe38093ae8affected · git
- f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 and later · before 9b405b3e7e131ee85dd78b9cc951b41f0828a333affected · git
- f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 and later · before 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4affected · git
- f6b6b52ef7a54160c0a4d2b56a58f84a2e5b33c5 and later · before 2b57e24d34b2dfc43c81942bb359d6315bf302fbaffected · git
- before 4.19not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90308Sep 17, 2026 · RDMA/erdma: Hold QP references for AE and CM processing31Monitor
- ← EarlierCVE-2026-90309Sep 17, 2026 · RDMA/erdma: Hold CQ references when processing EQ events31Monitor
- Later →CVE-2026-90312Sep 17, 2026 · bpf: Check load-acquire src ptr type before the load31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 23094544b8e8c43909fd61ca8866ecfe38093ae8 | Vendor (CNA) |
| Linux Linux | 2b57e24d34b2dfc43c81942bb359d6315bf302fb | Vendor (CNA) |
| Linux Linux | 4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4 | Vendor (CNA) |
| Linux Linux | 9b405b3e7e131ee85dd78b9cc951b41f0828a333 | Vendor (CNA) |
| Linux Linux | df002834cfd880b800fa607135e4bb2e403ce187 | Vendor (CNA) |
| Linux Linux | e67dad2cff9e4fedce69e752d515ef651d745a90 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2b57e24d34b2dfc43c81942bb359d6315bf302fb
- git.kernel.org/stable/c/4fa8915f40f744c6db2a3c25b2ae7d2dd64c77b4
- git.kernel.org/stable/c/9b405b3e7e131ee85dd78b9cc951b41f0828a333
- git.kernel.org/stable/c/df002834cfd880b800fa607135e4bb2e403ce187
- git.kernel.org/stable/c/e67dad2cff9e4fedce69e752d515ef651d745a90
Vendor advisories and official records. Exploit/PoC links are deliberately left out.