CVE-2026-92492: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-92492 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-92492 at a Glance
How to Fix CVE-2026-92492
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.
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-92492, 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
References
Frequently Asked Questions
What is CVE-2026-92492?
Which Software versions are affected?
What version fixes CVE-2026-92492?
What CWE is associated with CVE-2026-92492?
How can I check Maven dependencies for CVE-2026-92492?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-2x57-5mr8-cjxj",
"modified" : "2026-09-17T18:32:06Z",
"published" : "2026-09-17T18:32:06Z",
"aliases" : [ "CVE-2026-92492" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ncpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks\n\ncpufreq_cpu_get() returns NULL when no cpufreq policy is associated with\nthe requested CPU, for example because the CPU is offline or the policy\nhas already been torn down. Both amd_pstate_power_supply_notifier() and\namd_pstate_profile_set() acquire a policy via cpufreq_cpu_get() and then\npass that pointer to amd_pstate_get_balanced_epp() and\namd_pstate_set_epp(), which dereference it unconditionally. A racing\nCPU hotplug or driver teardown can therefore lead to a NULL pointer\ndereference on either of these dynamic EPP paths.\n\nThe third cpufreq_cpu_get() caller in this file, amd_pstate_verify(),\nalready handles the NULL case. Bring the two new callers in line with\nthat pattern: return NOTIFY_OK from the power-supply notifier (matching\nthe other \"nothing to do\" exits) and -ENODEV from amd_pstate_profile_set()\n(the usual cpufreq error for a missing CPU policy).\n\nFound by code inspection; not tested on hardware.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92492"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/39c0cf62fc7851a17782e7efe8dfb2948739c681"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/70c8c8b50d80f681f50ddcc66a9400dd87508913"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f4ade8d224756ab69f108204dde6777bac4664e4"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:17:51Z"
}
}