CVE-2023-53471: drm/amdgpu/gfx: disable gfx9 cp_ecc_error_irq only when enabling legacy gfx ras
Noroxi assessment
Priority: Monitor (action score 31/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.16% (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 20ca90ceda71ed90a4d6960acbe7d5e120b40c0d, 3d28af21a874c5123d1681c2d686627f7ff7e488, 4a76680311330aefe5074bed8f06afa354b85c48.
Low priority for now. Upgrade to Linux Linux 20ca90ceda71ed90a4d6960acbe7d5e120b40c0d, 3d28af21a874c5123d1681c2d686627f7ff7e488, 4a76680311330aefe5074bed8f06afa354b85c48 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/gfx: disable gfx9 cp_ecc_error_irq only when enabling legacy gfx ras gfx9 cp_ecc_error_irq is only enabled when legacy gfx ras is assert. So in gfx_v9_0_hw_fini, interrupt disablement for cp_ecc_error_irq should be executed under such condition, otherwise, an amdgpu_irq_put calltrace will occur. [ 7283.170322] RIP: 0010:amdgpu_irq_put+0x45/0x70 [amdgpu] [ 7283.170964] RSP: 0018:ffff9a5fc3967d00 EFLAGS: 00010246 [ 7283.170967] RAX: ffff98d88afd3040 RBX: ffff98d89da20000 RCX: 0000000000000000 [ 7283.170969] RDX: 0000000000000000 RSI: ffff98d89da2bef8 RDI: ffff98d89da20000 [ 7283.170971] RBP: ffff98d89da20000 R08: ffff98d89da2ca18 R09: 0000000000000006 [ 7283.170973] R10: ffffd5764243c008 R11: 0000000000000000 R12: 0000000000001050 [ 7283.170975] R13: ffff98d89da38978 R14: ffffffff999ae15a R15: ffff98d880130105 [ 7283.170978] FS: 0000000000000000(0000) GS:ffff98d996f00000(0000) knlGS:0000000000000000 [ 7283.170981] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7283.170983] CR2: 00000000f7a9d178 CR3: 00000001c42ea000 CR4: 00000000003506e0 [ 7283.170986] Call Trace: [ 7283.170988] <TASK> [ 7283.170989] gfx_v9_0_hw_fini+0x1c/0x6d0 [amdgpu] [ 7283.171655] amdgpu_device_ip_suspend_phase2+0x101/0x1a0 [amdgpu] [ 7283.172245] amdgpu_device_suspend+0x103/0x180 [amdgpu] [ 7283.172823] amdgpu_pmops_freeze+0x21/0x60 [amdgpu] [ 7283.173412] pci_pm_freeze+0x54/0xc0 [ 7283.173419] ? __pfx_pci_pm_freeze+0x10/0x10 [ 7283.173425] dpm_run_callback+0x98/0x200 [ 7283.173430] __device_suspend+0x164/0x5f0 v2: drop gfx11 as it's fixed in a different solution by retiring cp_ecc_irq funcs(Hawking)
- Published
- Oct 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.2 and later · before 5.4.243
- linux linux kernel5.5 and later · before 5.10.180
- linux linux kernel5.11 and later · before 5.15.112
- linux linux kernel5.16 and later · before 6.1.29
- linux linux kernel6.2 and later · before 6.2.16
- linux linux kernel6.3 and later · before 6.3.3
- linux linux kernel6.4
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 625d4112ea25dbad7ddf749fd5c1287ceffb2339affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 20ca90ceda71ed90a4d6960acbe7d5e120b40c0daffected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before cd3c0f7013c37cd24fc40b601319007f136c1201affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before f661ad53658a1ea35c004af1f5fbe25c4d1cdb08affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 3d28af21a874c5123d1681c2d686627f7ff7e488affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before efce310db74fdc6d2acd959f3582972ae4a8d7d5affected · git
- d38ceaf99ed015f2a0b9af3499791bd3a3daae21 and later · before 4a76680311330aefe5074bed8f06afa354b85c48affected · 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-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-2023-53468Oct 1, 2025 · ubifs: Fix memory leak in alloc_wbufs()22Monitor
- ← EarlierCVE-2023-53470Oct 1, 2025 · ionic: catch failure from devlink_alloc22Monitor
- Later →CVE-2023-53472Oct 1, 2025 · pwm: lpc32xx: Remove handling of PWM channels22Monitor
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 | 20ca90ceda71ed90a4d6960acbe7d5e120b40c0d | Vendor (CNA) |
| Linux Linux | 3d28af21a874c5123d1681c2d686627f7ff7e488 | Vendor (CNA) |
| Linux Linux | 4a76680311330aefe5074bed8f06afa354b85c48 | Vendor (CNA) |
| Linux Linux | 625d4112ea25dbad7ddf749fd5c1287ceffb2339 | Vendor (CNA) |
| Linux Linux | cd3c0f7013c37cd24fc40b601319007f136c1201 | Vendor (CNA) |
| Linux Linux | efce310db74fdc6d2acd959f3582972ae4a8d7d5 | Vendor (CNA) |
| Linux Linux | f661ad53658a1ea35c004af1f5fbe25c4d1cdb08 | 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.
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.
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
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/3d28af21a874c5123d1681c2d686627f7ff7e488
- git.kernel.org/stable/c/4a76680311330aefe5074bed8f06afa354b85c48
- git.kernel.org/stable/c/625d4112ea25dbad7ddf749fd5c1287ceffb2339
- git.kernel.org/stable/c/cd3c0f7013c37cd24fc40b601319007f136c1201
- git.kernel.org/stable/c/efce310db74fdc6d2acd959f3582972ae4a8d7d5
- git.kernel.org/stable/c/f661ad53658a1ea35c004af1f5fbe25c4d1cdb08
Vendor advisories and official records. Exploit/PoC links are deliberately left out.