CVE-2026-46220: drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0b91ea46bb68abf98a082bf239092253bbd6aaa2, 25e7d56a39657d56d1ea6d78992f7ed15dedb412, 4f7ca00fa91daf0795ec6b3b130c5ebba1f155fe; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0b91ea46bb68abf98a082bf239092253bbd6aaa2, 25e7d56a39657d56d1ea6d78992f7ed15dedb412, 4f7ca00fa91daf0795ec6b3b130c5ebba1f155fe; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.141.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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)
- Published
- May 28, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-617
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.12 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.140
- linux linux kernel6.7 and later · before 6.12.90
- linux linux kernel6.13 and later · before 6.18.32
- linux linux kernel6.19 and later · before 7.0.9
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before ecaa80318e900ca0c3f687742ede33b41cfd2f8eaffected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before 25e7d56a39657d56d1ea6d78992f7ed15dedb412affected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before d4c56932d29773e278be6a65a5384a36c95b89a4affected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before 4f7ca00fa91daf0795ec6b3b130c5ebba1f155feaffected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before d331fb241a4602253976ddd65144a8ba2b05665daffected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before 0b91ea46bb68abf98a082bf239092253bbd6aaa2affected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before a4fd82fb0757c180bf622907397c528b89a827b2affected · git
- 2130f89ced2cc0f5113bb427c1cbc7a4ca7729c7 and later · before 78d2e624fa073c14970aa097adcf3ea31c157a66affected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.90-1 | 6.12.90-1 |
| Debian:14 | linux | before 7.0.9-1 | 7.0.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46214May 28, 2026 · vsock/virtio: fix accept queue count leak on transport mismatch22Monitor
- ← EarlierCVE-2026-46216May 28, 2026 · drm/xe/hdcp: Add NULL check for media_gt in intel_hdcp_gsc_check_status()22Monitor
- Later →CVE-2026-46224May 28, 2026 · drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0b91ea46bb68abf98a082bf239092253bbd6aaa2 | Vendor (CNA) |
| Linux Linux | 25e7d56a39657d56d1ea6d78992f7ed15dedb412 | Vendor (CNA) |
| Linux Linux | 4f7ca00fa91daf0795ec6b3b130c5ebba1f155fe | Vendor (CNA) |
| Linux Linux | 78d2e624fa073c14970aa097adcf3ea31c157a66 | Vendor (CNA) |
| Linux Linux | a4fd82fb0757c180bf622907397c528b89a827b2 | Vendor (CNA) |
| Linux Linux | d331fb241a4602253976ddd65144a8ba2b05665d | Vendor (CNA) |
| Linux Linux | d4c56932d29773e278be6a65a5384a36c95b89a4 | Vendor (CNA) |
| Linux Linux | ecaa80318e900ca0c3f687742ede33b41cfd2f8e | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.141.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-3173927 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2026-5295227 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2026-461170 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
- CVE-2026-3139855 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2025-39803255 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2026-460271 days apartnet/smc: avoid early lgr access in smc_clc_wait_msg30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/25e7d56a39657d56d1ea6d78992f7ed15dedb412
- git.kernel.org/stable/c/4f7ca00fa91daf0795ec6b3b130c5ebba1f155fe
- git.kernel.org/stable/c/78d2e624fa073c14970aa097adcf3ea31c157a66
- git.kernel.org/stable/c/a4fd82fb0757c180bf622907397c528b89a827b2
- git.kernel.org/stable/c/d331fb241a4602253976ddd65144a8ba2b05665d
- git.kernel.org/stable/c/d4c56932d29773e278be6a65a5384a36c95b89a4
- git.kernel.org/stable/c/ecaa80318e900ca0c3f687742ede33b41cfd2f8e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.