GHSA-R39R-J9PR-WC8X
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-90178"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:11Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (coretemp) Fix core_data leak on CPUs without PTS\n\npdata-\u003ecore_data is allocated in init_temp_data() when the first core\ntemp_data of a package is created, but it is only released from\ndestroy_temp_data(), and only in the branch that handles the package\ntemp_data.\n\nPackage temp_data is created solely when the CPU supports\nX86_FEATURE_PTS. On a CPU without it, coretemp_cpu_online() never calls\ncoretemp_add_core() with pkg_flag set, so pdata-\u003epkg_data stays NULL.\ncoretemp_cpu_offline() then skips the removal of the package interface,\ndestroy_temp_data() is never called for package data, and the array is\nstill allocated when coretemp_device_remove() frees the platform data\nthat pointed at it.\n\nRelease the array in coretemp_device_remove(). destroy_temp_data() sets\npdata-\u003ecore_data to NULL when it frees it, so the added kfree() is a\nno-op on CPUs that do have PTS.\n\nTested on an Intel Core i5-1135G7. The driver was instrumented to log\nevery allocation and release of pdata-\u003ecore_data, and the PTS check in\ncoretemp_cpu_online() was patched out to emulate a CPU without package\nthermal support. Without this change the array was allocated and never\nreleased, and coretemp_device_remove() still saw a non-NULL pointer.\nWith it the array is released and the pointer accounting balances. On an\nunmodified build the release still happens via the package temp_data and\nthe added kfree() sees NULL, with no slab warnings over repeated module\nload and unload cycles.",
"id": "GHSA-r39r-j9pr-wc8x",
"modified": "2026-09-17T18:31:54Z",
"published": "2026-09-17T18:31:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90178"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0cd8450c257faa0cece0e0c43d3b55d1a389acc7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/86c1617b7d4b001b20a71deda3c791538a4fa6aa"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9b23a010a1e8232974617c412cb9f578f3378b70"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dc0d79b1be384e7f6a2308356afd10dcf3bf940f"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.