# CVE-2026-46220: drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission

> Unprivileged users can trigger a kernel panic via crafted GPU submissions, causing a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 14 Jun 2026
- **Also known as:** AZL-89054, BELL-CVE-2026-46220, DEBIAN-CVE-2026-46220, GHSA-5vh3-fx9f-223v, ROOT-OS-DEBIAN-11-CVE-2026-46220, ROOT-OS-DEBIAN-12-CVE-2026-46220, ROOT-OS-UBUNTU-2204-CVE-2026-46220, ROOT-OS-UBUNTU-2404-CVE-2026-46220, UBUNTU-CVE-2026-46220

## What is CVE-2026-46220?

CVE-2026-46220 is a medium-severity denial of service vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission

sdma_v4_0_ring_emit_fence() contains two BUG_ON(addr & 0x3) assertions
that verify fence writeback addresses are dword-aligned.  These
assertions can be reached from unprivileged userspace via crafted
DRM_IOCTL_AMDGPU_CS submissions, causing a fatal kernel panic in a
scheduler worker thread.

Replace both BUG_ON() calls with WARN_ON() to log the condition without
crashing the kernel.  A misaligned fence address at this point indicates
a driver bug, but crashing the kernel is never the correct response when
the assertion is reachable from userspace.

The CS IOCTL path is the correct place to filter invalid submissions;
the ring emission callback is too late to do anything about it.

(cherry picked from commit b90250bd933afd1ba94d86d6b13821997b22b18e)

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-46220?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46220?

Apply the vendor's patch.

## Is CVE-2026-46220 being exploited?

There is no known exploitation of CVE-2026-46220 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46220 and fix it if it is affected.

What it is: CVE-2026-46220 is a medium-severity denial of service vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46220 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46220/ (Markdown: https://insights.sbomify.com/CVE-2026-46220/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46220
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46220
- OSV: https://osv.dev/vulnerability/CVE-2026-46220

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46220/
Summaries are generated and may contain mistakes; the official description above is the record.