VulnerabilityPublished 28 May 2026Updated 6 Nov 2026

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

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in ecaa80318e900ca0c3f687742ede33b41cfd2f8e : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in ecaa80318e900ca0c3f687742ede33b41cfd2f8e, d331fb241a4602253976ddd65144a8ba2b05665d, d4c56932d29773e278be6a65a5384a36c95b89a4 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7, < ecaa80318e900ca0c3f687742ede33b41cfd2f8e	Fixed in ecaa80318e900ca0c3f687742ede33b41cfd2f8e
LinuxLinux	Affected ≥ 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7, < d331fb241a4602253976ddd65144a8ba2b05665d	Fixed in d331fb241a4602253976ddd65144a8ba2b05665d
LinuxLinux	Affected ≥ 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7, < d4c56932d29773e278be6a65a5384a36c95b89a4	Fixed in d4c56932d29773e278be6a65a5384a36c95b89a4
LinuxLinux	Affected ≥ 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7, < a4fd82fb0757c180bf622907397c528b89a827b2	Fixed in a4fd82fb0757c180bf622907397c528b89a827b2
LinuxLinux	Affected ≥ 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7, < 78d2e624fa073c14970aa097adcf3ea31c157a66	Fixed in 78d2e624fa073c14970aa097adcf3ea31c157a66
LinuxLinux	Affected ≥ 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7, < 25e7d56a39657d56d1ea6d78992f7ed15dedb412	Fixed in 25e7d56a39657d56d1ea6d78992f7ed15dedb412

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)

References

Community reviews

Loading reviews…