Skip to content
Threat Brief

← All advisories

CVE-2026-90178

Severity unknownNo known exploitationFix available

hwmon: (coretemp) Fix core_data leak on CPUs without PTS

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 1a793caf6f6991716cb07583ed7c27de84ef0cba before dc0d79b1be384e7f6a2308356afd10dcf3bf940fdc0d79b1be384e7f6a2308356afd10dcf3bf940fCVE Program
LinuxLinuxfrom 1a793caf6f6991716cb07583ed7c27de84ef0cba before 86c1617b7d4b001b20a71deda3c791538a4fa6aa86c1617b7d4b001b20a71deda3c791538a4fa6aaCVE Program
LinuxLinuxfrom 1a793caf6f6991716cb07583ed7c27de84ef0cba before 9b23a010a1e8232974617c412cb9f578f3378b709b23a010a1e8232974617c412cb9f578f3378b70CVE Program
LinuxLinuxfrom 1a793caf6f6991716cb07583ed7c27de84ef0cba before 0cd8450c257faa0cece0e0c43d3b55d1a389acc70cd8450c257faa0cece0e0c43d3b55d1a389acc7CVE Program
LinuxLinux6.9Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.110 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.52 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.6 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.9Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references