drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: disable sdma ecc irq only when sdma RAS is enabled in suspend sdma_v4_0_ip is shared on a few asics, but in sdma_v4_0_hw_fini, driver unconditionally disables ecc_irq which is only enabled on those asics enabling sdma ecc. This will introduce a warning in suspend cycle on those chips with sdma ip v4.0, while without sdma ecc. So this patch correct this. [ 7283.166354] RIP: 0010:amdgpu_irq_put+0x45/0x70 [amdgpu] [ 7283.167001] RSP: 0018:ffff9a5fc3967d08 EFLAGS: 00010246 [ 7283.167019] RAX: ffff98d88afd3770 RBX: 0000000000000001 RCX: 0000000000000000 [ 7283.167023] RDX: 0000000000000000 RSI: ffff98d89da30390 RDI: ffff98d89da20000 [ 7283.167025] RBP: ffff98d89da20000 R08: 0000000000036838 R09: 0000000000000006 [ 7283.167028] R10: ffffd5764243c008 R11: 0000000000000000 R12: ffff98d89da30390 [ 7283.167030] R13: ffff98d89da38978 R14: ffffffff999ae15a R15: ffff98d880130105 [ 7283.167032] FS: 0000000000000000(0000) GS:ffff98d996f00000(0000) knlGS:0000000000000000 [ 7283.167036] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7283.167039] CR2: 00000000f7a9d178 CR3: 00000001c42ea000 CR4: 00000000003506e0 [ 7283.167041] Call Trace: [ 7283.167046] <TASK> [ 7283.167048] sdma_v4_0_hw_fini+0x38/0xa0 [amdgpu] [ 7283.167704] amdgpu_device_ip_suspend_phase2+0x101/0x1a0 [amdgpu] [ 7283.168296] amdgpu_device_suspend+0x103/0x180 [amdgpu] [ 7283.168875] amdgpu_pmops_freeze+0x21/0x60 [amdgpu] [ 7283.169464] pci_pm_freeze+0x54/0xc0
- Published
- Oct 22, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 9th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.2affected
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 3decf3a750a924362bf4e2680dd3b07242fe56e8affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before c1420276be7a98df0074584bb9c1709cbc1a9df5affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 823787470e320f90372c3ef506769520026c571faffected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 2a179117a3b29e7136e4045c57090a05bb97f373affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 71e1f44077db83e205db70a684c1f2c5d2247174affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before c5123c193696bf97fdf259c825ebfac517b54e44affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 8b229ada2669b74fdae06c83fbfda5a5a99fc253affected · git
- before 4.2not affected · semver
- 5.4.243 and later · up to and including 5.4.*not 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.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 2a179117a3b29e7136e4045c57090a05bb97f373 | Vendor (CNA) |
| Linux Linux | 3decf3a750a924362bf4e2680dd3b07242fe56e8 | Vendor (CNA) |
| Linux Linux | 71e1f44077db83e205db70a684c1f2c5d2247174 | Vendor (CNA) |
| Linux Linux | 823787470e320f90372c3ef506769520026c571f | Vendor (CNA) |
| Linux Linux | 8b229ada2669b74fdae06c83fbfda5a5a99fc253 | Vendor (CNA) |
| Linux Linux | c1420276be7a98df0074584bb9c1709cbc1a9df5 | Vendor (CNA) |
| Linux Linux | c5123c193696bf97fdf259c825ebfac517b54e44 | Vendor (CNA) |
| debian:linux | 6.1.37-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
No nightly-computed relations.
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).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/2a179117a3b29e7136e4045c57090a05bb97f373
- git.kernel.org/stable/c/3decf3a750a924362bf4e2680dd3b07242fe56e8
- git.kernel.org/stable/c/71e1f44077db83e205db70a684c1f2c5d2247174
- git.kernel.org/stable/c/823787470e320f90372c3ef506769520026c571f
- git.kernel.org/stable/c/8b229ada2669b74fdae06c83fbfda5a5a99fc253
- git.kernel.org/stable/c/c1420276be7a98df0074584bb9c1709cbc1a9df5
- git.kernel.org/stable/c/c5123c193696bf97fdf259c825ebfac517b54e44
Vendor advisories and official records. Exploit/PoC links are deliberately left out.