CVE-2026-90178

Not scored yetLast modified Oct 19, 2026

Description

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.

Metrics

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1a793caf6f6991716cb07583ed7c27de84ef0cba, < dc0d79b1be384e7f6a2308356afd10dcf3bf940f; >= 1a793caf6f6991716cb07583ed7c27de84ef0cba, < 86c1617b7d4b001b20a71deda3c791538a4fa6aa; >= 1a793caf6f6991716cb07583ed7c27de84ef0cba, < 9b23a010a1e8232974617c412cb9f578f3378b70; >= 1a793caf6f6991716cb07583ed7c27de84ef0cba, < 0cd8450c257faa0cece0e0c43d3b55d1a389acc7
LinuxLinux6.9

References

Timeline

Published
Sep 17, 2026
Last modified
Oct 19, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-90179In the Linux kernel, the following vulnerability has been resolved: apparmor: fix deadlock in complain-mode change_hat The use of change_hCVE-2026-90188.8The Easy Elements for Elementor – Addons & Website Templates plugin for WordPress is vulnerable to Privilege Escalation in all versions up tCVE-2026-90180In the Linux kernel, the following vulnerability has been resolved: block: mtip32xx: synchronize ioctls with device removal The ioctl handCVE-2026-90181In the Linux kernel, the following vulnerability has been resolved: ublk: avoid teardown retry loop on xarray allocation failure __ublk_shCVE-2026-90182In the Linux kernel, the following vulnerability has been resolved: blk-iocost: clear delay state when freeing policy data iocg_kick_delayCVE-2026-90183In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: clear delay state when freeing policy data io.latency cCVE-2026-90184In the Linux kernel, the following vulnerability has been resolved: null_blk: serialize configfs attribute updates with device setup The aCVE-2026-90185In the Linux kernel, the following vulnerability has been resolved: null_blk: serialize configfs attribute stores with the lock The NULLB_CVE-2026-90186In the Linux kernel, the following vulnerability has been resolved: null_blk: reject per-device queue resize for shared tag set When shareCVE-2026-90187In the Linux kernel, the following vulnerability has been resolved: null_blk: free zones array on device power-off null_init_zoned_dev() aCVE-2026-90188In the Linux kernel, the following vulnerability has been resolved: null_blk: free global tag_set on init error path If shared_tags is enaCVE-2026-90189In the Linux kernel, the following vulnerability has been resolved: null_blk: register configfs subsystem after creating default devices I