{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92492 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92492 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92492 and fix it if it is affected.\n\nWhat it is: CVE-2026-92492 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-92492 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-92492/ (Markdown: https://insights.sbomify.com/CVE-2026-92492/index.md)","id":"CVE-2026-92492","markdown":"https://insights.sbomify.com/CVE-2026-92492/index.md","name":"CVE-2026-92492","record":{"aliases":["DEBIAN-CVE-2026-92492","GHSA-2x57-5mr8-cjxj","UBUNTU-CVE-2026-92492"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A race condition in the Linux kernel's AMD P-State driver can cause a NULL pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks","id":"CVE-2026-92492","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"cpufreq: amd-pstate-ut: Skip tests when amd-pstate driver is not active","id":"CVE-2026-92493"},"packages":[],"prev":{"headline":"firmware: arm_scmi: Roll back partial protocol table registration","id":"CVE-2026-92491"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's AMD P-State driver can cause a NULL pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-92492/"}