GHSA-2X57-5MR8-CJXJ
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks
cpufreq_cpu_get() returns NULL when no cpufreq policy is associated with the requested CPU, for example because the CPU is offline or the policy has already been torn down. Both amd_pstate_power_supply_notifier() and amd_pstate_profile_set() acquire a policy via cpufreq_cpu_get() and then pass that pointer to amd_pstate_get_balanced_epp() and amd_pstate_set_epp(), which dereference it unconditionally. A racing CPU hotplug or driver teardown can therefore lead to a NULL pointer dereference on either of these dynamic EPP paths.
The third cpufreq_cpu_get() caller in this file, amd_pstate_verify(), already handles the NULL case. Bring the two new callers in line with that pattern: return NOTIFY_OK from the power-supply notifier (matching the other "nothing to do" exits) and -ENODEV from amd_pstate_profile_set() (the usual cpufreq error for a missing CPU policy).
Found by code inspection; not tested on hardware.
{
"affected": [],
"aliases": [
"CVE-2026-92492"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:51Z",
"severity": null
},
"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.",
"id": "GHSA-2x57-5mr8-cjxj",
"modified": "2026-09-17T18:32:06Z",
"published": "2026-09-17T18:32:06Z",
"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"
}
],
"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.