{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98389 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98389 is a vulnerability in Linux, published on 14 Oct 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-98389 and fix it if it is affected.\n\nWhat it is: CVE-2026-98389 is a vulnerability in Linux, published on 14 Oct 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-98389 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-98389/ (Markdown: https://insights.sbomify.com/CVE-2026-98389/index.md)","id":"CVE-2026-98389","markdown":"https://insights.sbomify.com/CVE-2026-98389/index.md","name":"CVE-2026-98389","record":{"aliases":["AZL-108093","BELL-CVE-2026-98389","DEBIAN-CVE-2026-98389","GHSA-f67h-8737-2vhm","UBUNTU-CVE-2026-98389"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A race condition in the AMD GPU driver during reset can cause a kernel assertion failure and system crash, requiring a local attacker to trigger GPU resets.","user_interaction":"not_required","vuln_class":"race_condition"},"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\ndrm/amdgpu: skip gfx switch_power_profile during GPU reset\n\nDuring resume from GPU reset, the gfx idle work may invoke switch_power_profile\nbefore the reset completes. This causes the following assert error because the\nregister access occurs without first releasing the GPU reset semaphore:\n\n[ 1576.768935] CR2: 0000559ea133ead0 CR3: 00000002e6c42000 CR4: 0000000000350ef0\n[ 1576.768940] Call Trace:\n[ 1576.768944]  \u003cTASK\u003e\n[ 1576.768953]  amdgpu_device_rreg+0x21/0x50 [amdgpu]\n[ 1576.769158]  smu_msg_v1_send_msg+0x1a4/0x6e0 [amdgpu]\n[ 1576.769437]  smu_cmn_send_smc_msg_with_params_ext+0xba/0x120 [amdgpu]\n[ 1576.769721]  smu_cmn_send_smc_msg_with_param+0x33/0x40 [amdgpu]\n[ 1576.769993]  smu_v13_0_0_set_power_profile_mode+0x192/0x2b0 [amdgpu]\n[ 1576.770267]  smu_bump_power_profile_mode+0x5d/0x80 [amdgpu]\n[ 1576.770538]  smu_switch_power_profile+0xa4/0xf0 [amdgpu]\n[ 1576.770839]  amdgpu_dpm_switch_power_profile+0x6f/0x90 [amdgpu]\n[ 1576.771210]  amdgpu_gfx_profile_idle_work_handler+0xe9/0x130 [amdgpu]\n[ 1576.771460]  process_one_work+0x23e/0x6f0\n[ 1576.771491]  worker_thread+0x1c4/0x380\n[ 1576.771506]  kthread+0x10c/0x150\n[ 1576.771512]  ? __pfx_worker_thread+0x10/0x10\n[ 1576.771518]  ? __pfx_kthread+0x10/0x10\n[ 1576.771530]  ret_from_fork+0x314/0x390\n[ 1576.771537]  ? __pfx_kthread+0x10/0x10\n[ 1576.771546]  ret_from_fork_asm+0x1a/0x30\n\n(cherry picked from commit d93b1ff538ce9750c01e0dd0aa62575579c0fc08)","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":"drm/amdgpu: skip gfx switch_power_profile during GPU reset","id":"CVE-2026-98389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"x86/amd_node: Avoid divide by zero on virtualized systems","id":"CVE-2026-98390"},"packages":[],"prev":{"headline":"exec: do_close_on_exec() before taking exec_update_lock","id":"CVE-2026-98388"},"products":["Linux"],"published":"2026-10-14","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-26","vendors":["Linux"]},"summary":"A race condition in the AMD GPU driver during reset can cause a kernel assertion failure and system crash, requiring a local attacker to trigger GPU resets.","url":"https://insights.sbomify.com/CVE-2026-98389/"}