What is CVE-2023-53237?

CVE-2023-53237 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 6.1.26 onward and patched in 6.1.29, 6.2.16, 6.3.3 and others. CVE-2023-53237 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2023-53237?

CVE-2023-53237 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2023-53237?

Yes, CVE-2023-53237 has been patched. Fixed versions include 6.1.29, 6.2.16, 6.3.3 and others. If you are running Linux kernel 6.1.26 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-53237 actively exploited?

CVE-2023-53237 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2023-53237

Medium

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

Package Linux Kernel

Published 2025-09-15

Last modified 2026-01-14

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 6.1.26, 6.2.13, 6.3 and later are affected. Fixed in 6.1.29, 6.2.16, 6.3.3, 6.4 and their respective stable series.

Affected from

≥ 6.1.26 ≥ 6.2.13 ≥ 6.3

Fixed in

✓ 6.1.29 6.1.x ✓ 6.2.16 6.2.x ✓ 6.3.3 6.3.x ✓ 6.4

References

4 total

Kernel Git
https://git.kernel.org/stable/c/02e6cb9b3aeffc6b0e3955f6e0346293e2415cbc

Patch
Kernel Git
https://git.kernel.org/stable/c/13af556104fa93b1945c70bbf8a0a62cd2c92879

Patch
Kernel Git
https://git.kernel.org/stable/c/396401bc035ff5bf0c7b29c67caa10040eb3fb62

Patch
Kernel Git
https://git.kernel.org/stable/c/79038b78af931908d6f5d4e279d3afe32e7c840b

Patch

Details

CVE ID CVE-2023-53237

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2025-09-15

Modified 2026-01-14

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2023-53237?

CVE-2023-53237 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.1.26 onward and has been patched in 6.1.29, 6.2.16, 6.3.3 and others. CVE-2023-53237 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-53237?

CVE-2023-53237 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2023-53237?

Yes. CVE-2023-53237 has been patched. Fixed versions include 6.1.29, 6.2.16, 6.3.3 and others. If you are running Linux kernel 6.1.26 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-53237 actively exploited?

No. CVE-2023-53237 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.