CVE-2023-53237
drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v11_0_hw_fini
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v11_0_hw_fini The gmc.ecc_irq is enabled by firmware per IFWI setting, and the host driver is not privileged to enable/disable the interrupt. So, it is meaningless to use the amdgpu_irq_put function in gmc_v11_0_hw_fini, which also leads to the call trace. [ 102.980303] Call Trace: [ 102.980303] <TASK> [ 102.980304] gmc_v11_0_hw_fini+0x54/0x90 [amdgpu] [ 102.980357] gmc_v11_0_suspend+0xe/0x20 [amdgpu] [ 102.980409] amdgpu_device_ip_suspend_phase2+0x240/0x460 [amdgpu] [ 102.980459] amdgpu_device_ip_suspend+0x3d/0x80 [amdgpu] [ 102.980520] amdgpu_device_pre_asic_reset+0xd9/0x490 [amdgpu] [ 102.980573] amdgpu_device_gpu_recover.cold+0x548/0xce6 [amdgpu] [ 102.980687] amdgpu_debugfs_reset_work+0x4c/0x70 [amdgpu] [ 102.980740] process_one_work+0x21f/0x3f0 [ 102.980741] worker_thread+0x200/0x3e0 [ 102.980742] ? process_one_work+0x3f0/0x3f0 [ 102.980743] kthread+0xfd/0x130 [ 102.980743] ? kthread_complete_and_exit+0x20/0x20 [ 102.980744] ret_from_fork+0x22/0x30
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
- CWE-noinfo Not enough information
Affected products
- affected bef774effb278ff0b65ea2dbaa1ab32ba6a1dc13 – < 02e6cb9b3aeffc6b0e3955f6e0346293e2415cbc
- affected 56a03f64fedf49a4f81c5605167b6e7bb0300a59 – < 396401bc035ff5bf0c7b29c67caa10040eb3fb62
- affected c8b5a95b570949536a2b75cd8fc4f1de0bc60629 – < 79038b78af931908d6f5d4e279d3afe32e7c840b
- affected c8b5a95b570949536a2b75cd8fc4f1de0bc60629 – < 13af556104fa93b1945c70bbf8a0a62cd2c92879
- affected 6.1.26 – < 6.1.29
- affected 6.2.13 – < 6.2.16
- affected 6.3
- unaffected < 6.3
- unaffected 6.1.29 – ≤ 6.1.*
- unaffected 6.2.16 – ≤ 6.2.*
- unaffected 6.3.3 – ≤ 6.3.*
- unaffected 6.4 – ≤ *
References (4)
- https://git.kernel.org/stable/c/02e6cb9b3aeffc6b0e3955f6e0346293e2415cbc (opens in a new tab)
- https://git.kernel.org/stable/c/396401bc035ff5bf0c7b29c67caa10040eb3fb62 (opens in a new tab)
- https://git.kernel.org/stable/c/79038b78af931908d6f5d4e279d3afe32e7c840b (opens in a new tab)
- https://git.kernel.org/stable/c/13af556104fa93b1945c70bbf8a0a62cd2c92879 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2023-53237)Record last updated .