{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92493 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92493 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-92493 and fix it if it is affected.\n\nWhat it is: CVE-2026-92493 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-92493 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-92493/ (Markdown: https://insights.sbomify.com/CVE-2026-92493/index.md)","id":"CVE-2026-92493","markdown":"https://insights.sbomify.com/CVE-2026-92493/index.md","name":"CVE-2026-92493","record":{"aliases":["AZL-101990","BELL-CVE-2026-92493","DEBIAN-CVE-2026-92493","GHSA-96fv-8xm5-286m","UBUNTU-CVE-2026-92493"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"Loading the amd_pstate_ut module on Intel systems causes a kernel crash due to a null pointer dereference, requiring root access to trigger.","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-ut: Skip tests when amd-pstate driver is not active\n\nThe crash issue may occur when modprobe amd_pstate_ut on intel platform.\n\n   amd_pstate_ut: 1    amd_pstate_ut_acpi_cpc_valid  success!\n   amd_pstate_ut: 2    amd_pstate_ut_check_enabled   success!\n   BUG: kernel NULL pointer dereference, address: 0000000000000080\n   #PF: supervisor read access in kernel mode\n   #PF: error_code(0x0000) - not-present page\n   PGD 0 P4D 0\n   Oops: 0000 [#1] SMP NOPTI\n   CPU: 0 PID: 20300 Comm: modprobe\n   Kdump: loaded Tainted: G O 6.6.0-0010.rc1.ctl4.x86_64 #1\n   Hardware name: FiberHome R2200 V5/Xeon Boards, BIOS 3.1a 02/24/2020\n   RIP: 0010:amd_pstate_ut_check_perf+0x141/0x280 [amd_pstate_ut]\n   Call Trace:\n    \u003cTASK\u003e\n    amd_pstate_ut_init+0x1b/0xff0 [amd_pstate_ut]\n    ? __pfx_amd_pstate_ut_init+0x10/0x10 [amd_pstate_ut]\n    do_one_initcall+0x42/0x2e0\n    ? kmalloc_trace+0x26/0x90\n    do_init_module+0x60/0x240\n    __se_sys_init_module+0x185/0x1c0\n    do_syscall_64+0x62/0x190\n    entry_SYSCALL_64_after_hwframe+0x76/0x7e\n    \u003c/TASK\u003e\n\nAdd state detection to amd pstate driver to prevent amd_pstate_ut driver\nfrom testing on non-AMD platforms.\n\n(ML: adjust title)","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-ut: Skip tests when amd-pstate driver is not active","id":"CVE-2026-92493","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":"ext4: fix buffer_head leak in ext4_init_orphan_info","id":"CVE-2026-92494"},"packages":[],"prev":{"headline":"cpufreq/amd-pstate: handle missing policy in dynamic EPP callbacks","id":"CVE-2026-92492"},"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":"Loading the amd_pstate_ut module on Intel systems causes a kernel crash due to a null pointer dereference, requiring root access to trigger.","url":"https://insights.sbomify.com/CVE-2026-92493/"}