CVE-2026-90178: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-r39r-j9pr-wc8x
Share
Published
Advisory Summary

CVE-2026-90178 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-90178 at a Glance

CVE Identifier CVE-2026-90178
GHSA Identifier GHSA-r39r-j9pr-wc8x
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-90178

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-90178, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-90178 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90178
git.kernel.org/stable/c/0cd8450c25... WEB
https://git.kernel.org/stable/c/0cd8450c257faa0cece0e0c43d3b55d1a389acc7
git.kernel.org/stable/c/86c1617b7d... WEB
https://git.kernel.org/stable/c/86c1617b7d4b001b20a71deda3c791538a4fa6aa
git.kernel.org/stable/c/9b23a010a1... WEB
https://git.kernel.org/stable/c/9b23a010a1e8232974617c412cb9f578f3378b70
git.kernel.org/stable/c/dc0d79b1be... WEB
https://git.kernel.org/stable/c/dc0d79b1be384e7f6a2308356afd10dcf3bf940f

Frequently Asked Questions

What is CVE-2026-90178?
CVE-2026-90178 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-90178?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90178?
CVE-2026-90178 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90178?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r39r-j9pr-wc8x",
  "modified" : "2026-09-17T18:31:54Z",
  "published" : "2026-09-17T18:31:54Z",
  "aliases" : [ "CVE-2026-90178" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (coretemp) Fix core_data leak on CPUs without PTS\n\npdata->core_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->pkg_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->core_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->core_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.",
  "severity" : [ ],
  "affected" : [ ],
  "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"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:11Z"
  }
}