CVE-2023-53308: In the Linux kernel, the following vulnerability has been resolved: net: fec: Better handle pm_runtime_get() failing in .remove() In the (unlikely) ...

Description

In the Linux kernel, the following vulnerability has been resolved: net: fec: Better handle pm_runtime_get() failing in .remove() In the (unlikely) event that pm_runtime_get() (disguised as pm_runtime_resume_and_get()) fails, the remove callback returned an error early. The problem with this is that the driver core ignores the error value and continues removing the device. This results in a resource leak. Worse the devm allocated resources are freed and so if a callback of the driver is called later the register mapping is already gone which probably results in a crash.

Metrics

CVSS 3.1

7.8/10

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

EPSS Probability

0.15%

4.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions	Update
Linux	Linux Kernel	>= 4.9.206, < 4.10	—
Linux	Linux Kernel	>= 4.14.158, < 4.14.316	—
Linux	Linux Kernel	>= 4.19.88, < 4.19.284	—
Linux	Linux Kernel	>= 5.3.15, < 5.4	—
Linux	Linux Kernel	>= 5.4.1, < 5.4.244	—
Linux	Linux Kernel	>= 5.5, < 5.10.181	—
Linux	Linux Kernel	>= 5.11, < 5.15.113	—
Linux	Linux Kernel	>= 5.16, < 6.1.30	—
Linux	Linux Kernel	>= 6.2, < 6.3.4	—
Linux	Linux Kernel	5.4	—
Linux	Linux Kernel	6.4	Rc1

References

Timeline

Published: Sep 16, 2025
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2023-53308?

In the Linux kernel, the following vulnerability has been resolved: net: fec: Better handle pm_runtime_get() failing in .remove() In the (unlikely) event that pm_runtime_get() (disguised as pm_runtime_resume_and_get()) fails, the remove callback returned an error early. The problem with this is that the driver core ignores the error value and continues removing the device. This results in a resource leak. Worse the devm allocated resources are freed and so if a callback of the driver is called later the register mapping is already gone which probably results in a crash.

How severe is CVE-2023-53308?

CVE-2023-53308 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.15% probability of exploitation in the next 30 days.

How do I fix CVE-2023-53308?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.