Look up another CVE · open CVE-2026-92504 in the interactive tracker
CVE-2026-92504
thermal: intel: int3400: clean up ODVP on probe failures
Published 2026-09-17 (31 days 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-92504 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-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
evaluate_odvp() creates per-ODVP sysfs files before the thermal zone and later probe resources are registered. The current unwind path only calls cleanup_odvp() from the late sysfs failure path, so failures after evaluate_odvp() but before that label, including thermal_tripless_zone_device_register() failures, leave the ODVP files and storage behind. Move the ODVP cleanup to the common ART/TRT unwind path so every failure after evaluate_odvp() releases the ODVP state. Also clear the cached ODVP pointers in cleanup_odvp(), because evaluate_odvp() can already call it for partial setup failures while probe continues.
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/intel/int340x_thermal/int3400_thermal.c
- What this is
- THERMALMAINTAINERS section matched on drivers/thermal/ · linux-pm@vger.kernel.org · Supported
- Kernel module
- int3400_thermal
Check it on the machine
grep -wE 'CONFIG_INT340X_THERMAL|CONFIG_THERMAL' /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.
lsmod | grep -w int3400_thermalPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
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.
- bookwormMnot built on arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, i386/686, i386/686-pae, i386/rt/686-pae, ppc64el/powerpc64le
- trixieMnot built on arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- forky, sidMnot built on arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- bookworm · linux-6.12Mnot built on arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k
- M
- a module where it is built at all; some flavours do not build it
- Build switches
- CONFIG_INT340X_THERMAL, CONFIG_THERMAL
- 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-09-17 (31 days ago)source
- CVSS
- 7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.15%, higher than 3.7% 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.8 | 5.10.270 | 5798c714fccf |
| 5.8 | 5.15.221 | bfd6df12ce67 |
| 5.8 | 6.1.188 | ad13e550ce51 |
| 5.8 | 6.6.157 | 08df725b9275 |
| 5.8 | 6.12.110 | bc0e96267a67 |
| 5.8 | 6.18.52 | d7b025d3fdf3 |
| 5.8 | 7.2.6 | 169772cd2147 |
| 5.8 | 7.3 | d83dc9ce57a7 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-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
- evaluate_odvp() in int3400_thermal_probe() creates odvpN attributes on the INT3400/INTC104x ACPI platform device; after a failed unwind the UAF is hit by reading those files in odvp_show(), not by a network or radio protocol payload.
- AC:HAttack complexity, high
- The leak runs only when int3400_thermal_probe() fails after evaluate_odvp() but before the old free_sysfs label (thermal_tripless_zone_device_register(), sysfs_create_group() for uuids/imok, or device_create_bin_file()), or when evaluate_odvp() itself fails after allocating attrs; those are -ENOMEM/kernfs errors the attacker cannot force.
- PR:LPrivileges required, low
- evaluate_odvp() creates each odvpN with mode 0444 on priv->pdev->dev.kobj; after probe kfree(priv) via free_art_trt without cleanup_odvp(), an unprivileged local user can open those leftover files and run odvp_show() with no CAP_SYS_ADMIN.
- UI:NUser interaction, none
- The attacker reads the leftover odvpN sysfs attributes themselves; no other user must mount media, bind int3400_thermal, or confirm a prompt.
- S:UScope, unchanged
- odvp_show() dereferences the probe-freed int3400_thermal_priv in the host kernel; this is not a VM, IOMMU, or sandbox escape.
- C:HConfidentiality impact, high
- odvp_show() evaluates odvp_attr->priv->odvp[odvp_attr->odvp] after int3400_thermal_probe() kfree(priv) on free_art_trt, a slab UAF of int3400_thermal_priv that discloses kernel memory once that object is reclaimed.
- I:HIntegrity impact, high
- cleanup_odvp() used to leave priv->odvp/priv->odvp_attrs set after evaluate_odvp()'s out_err path; a later evaluate_odvp() from int3400_thermal_change_mode() or INT3400_ODVP_CHANGED then writes ACPI integers through the freed odvp buffer, and remove-path cleanup_odvp() double-frees it.
- A:HAvailability impact, high
- odvp_show() dereferencing the freed priv, and evaluate_odvp() writing through a dangling priv->odvp, oops or panic the kernel.