CVE-2026-90178hwmon: (coretemp) Fix core_data leak on CPUs without PTS
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Fix core_data leak on CPUs without PTS pdata->core_data is allocated in init_temp_data() when the first core temp_data of a package is created, but it is only released from destroy_temp_data(), and only in the branch that handles the package temp_data. Package temp_data is created solely when the CPU supports X86_FEATURE_PTS. On a CPU without it, coretemp_cpu_online() never calls coretemp_add_core() with pkg_flag set, so pdata->pkg_data stays NULL. coretemp_cpu_offline() then skips the removal of the package interface, destroy_temp_data() is never called for package data, and the array is still allocated when coretemp_device_remove() frees the platform data that pointed at it. Release the array in coretemp_device_remove(). destroy_temp_data() sets pdata->core_data to NULL when it frees it, so the added kfree() is a no-op on CPUs that do have PTS. Tested on an Intel Core i5-1135G7. The driver was instrumented to log every allocation and release of pdata->core_data, and the PTS check in coretemp_cpu_online() was patched out to emulate a CPU without package thermal support. Without this change the array was allocated and never released, and coretemp_device_remove() still saw a non-NULL pointer. With it the array is released and the pointer accounting balances. On an unmodified build the release still happens via the package temp_data and the added kfree() sees NULL, with no slab warnings over repeated module load and unload cycles.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1a793caf6f6991716cb07583ed7c27de84ef0cba before dc0d79b1be384e7f6a2308356afd10dcf3bf940f; from 1a793caf6f6991716cb07583ed7c27de84ef0cba before 86c1617b7d4b001b20a71deda3c791538a4fa6aa; from 1a793caf6f6991716cb07583ed7c27de84ef0cba before 9b23a010a1e8232974617c412cb9f578f3378b70; 1a793caf6f6991716cb07583ed7c27de84ef0cba builds before 0cd8450c257faa0cece0e0c43d3b55d1a389acc7 | CNA record |
References
- https://git.kernel.org/stable/c/dc0d79b1be384e7f6a2308356afd10dcf3bf940f
- https://git.kernel.org/stable/c/86c1617b7d4b001b20a71deda3c791538a4fa6aa
- https://git.kernel.org/stable/c/9b23a010a1e8232974617c412cb9f578f3378b70
- https://git.kernel.org/stable/c/0cd8450c257faa0cece0e0c43d3b55d1a389acc7
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.