Look up another CVE · open CVE-2026-74604 in the interactive tracker
CVE-2026-74604
Revert "thermal/drivers/hwmon: Cleanup coding style a bit"
Published 2026-08-22 (2 months ago) by the Linux kernel CNA. Subsystem drivers/thermal. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-74604 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4777-1 · 2026-09-08 · text | 6.1.187-1 | Update the kernel and reboot. DLA-4777-1 shipped the fix on 2026-09-08, in 6.1.187-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6466-1 · 2026-08-25 · text | 6.12.105-1 | Update the kernel and reboot. DSA-6466-1 shipped the fix on 2026-08-25, in 6.12.105-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.9-1 | Update the kernel and reboot. Fixed in 7.1.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4788-1 · 2026-09-19 · text | 6.12.107-1~deb12u1 | Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Revert commit 030a48b0f6ce ("thermal/drivers/hwmon: Cleanup coding style a bit") that introduced a use-after-free into the error path of thermal_add_hwmon_sysfs() by removing a valid check from it.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/thermal/thermal_hwmon.c
- What this is
- THERMALMAINTAINERS section matched on drivers/thermal/ · linux-pm@vger.kernel.org · Supported
Check it on the machine
grep -wE 'CONFIG_THERMAL|CONFIG_THERMAL_HWMON' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookworm, trixie, forky, sid, bookworm · linux-6.12Ynot built on amd64/cloud-amd64, arm64/cloud-arm64
- Y
- built in where it is built at all; some flavours do not build it
- Build switches
- CONFIG_THERMAL, CONFIG_THERMAL_HWMON
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-22 (2 months ago)source
- CVSS
- 8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 2.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/thermal
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.11 | 5.15.216 | 2434f4765da8 |
| 5.11 | 6.1.183 | b4c01ae6dd56 |
| 5.11 | 6.6.152 | 999e573212d5 |
| 5.11 | 6.12.104 | 6a48ee9a5bda |
| 5.11 | 6.18.45 | 8d34019d1413 |
| 5.11 | 7.1.9 | 6b446d335ba1 |
| 5.11 | 7.2 | ff8da20b6f47 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4788-1 | 2026-09-19 | bookworm 6.12.107-1~deb12u1 | tracker |
| DLA-4777-1 | 2026-09-08 | bookworm 6.1.187-1 | tracker |
| DSA-6466-1 | 2026-08-25 | trixie 6.12.105-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is in thermal_add_hwmon_sysfs() during thermal zone/hwmon driver registration; it is only reachable from kernel thermal driver probe/init paths, not from network protocols or physical buses.
- AC:LAttack complexity, low
- When a second thermal zone shares an existing hwmon type and registration fails, the error path deterministically kfree()s a still-linked hwmon object, leaving a dangling entry that any later sysfs access can hit without winning a race.
- PR:NPrivileges required, none
- No privileges are needed to exploit the resulting UAF: hwmon temp attributes are world-readable (0444) and unprivileged local processes routinely read /sys/class/hwmon on phones, servers, and embedded devices after latent corruption during multi-sensor thermal probe.
- UI:NUser interaction, none
- Exploitation requires no victim interaction beyond normal system operation; reading thermal sensors or subsequent kernel hwmon operations can trigger use of the freed object automatically.
- S:UScope, unchanged
- Impact is confined to kernel memory corruption and privilege escalation within the host kernel; it does not cross VM, container, or IOMMU security boundaries by itself.
- C:HConfidentiality impact, high
- The use-after-free of struct thermal_hwmon_device leaves a dangling list entry and device pointer; subsequent sysfs reads or thermal hwmon operations can dereference attacker-influencable freed heap memory, enabling arbitrary kernel memory disclosure.
- I:HIntegrity impact, high
- Heap UAF on a long-lived thermal_hwmon_device structure adjacent to list pointers and device objects provides standard kernel heap corruption primitives that can be developed into arbitrary write and local privilege escalation.
- A:HAvailability impact, high
- Use-after-free in kernel thermal/hwmon registration can cause immediate kernel oops/panic on access to the freed hwmon device, and repeated or concurrent sysfs access can reliably crash or hang the system.