CVE-2023-53596: drivers: base: Free devm resources when unregistering a device

Published Oct 4, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drivers: base: Free devm resources when unregistering a device

In the current code, devresreleaseall() only gets called if the device has a bus and has been probed.

This leads to issues when using bus-less or driver-less devices where the device might never get freed if a managed resource holds a reference to the device. This is happening in the DRM framework for example.

We should thus call devresreleaseall() in the devicedel() function to make sure that the device-managed actions are properly executed when the device is unregistered, even if it has neither a bus nor a driver.

This is effectively the same change than commit 2f8d16a996da ("devres: release resources on devicedel()") that got reverted by commit a525a3ddeaca ("driver core: free devres in devicerelease") over memory leaks concerns.

This patch effectively combines the two commits mentioned above to release the resources both on devicedel() and devicerelease() and get the best of both worlds.

Affected Software

6 affected components
Linux Kernel
Linux Linux kernel>=3.7<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.53
Linux Linux kernel>=6.2<6.4.16
Linux Linux kernel>=6.5<6.5.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 2f8d16a996da
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch a525a3ddeaca

Event History

Oct 4, 2025
CVE Published
via MITRE·03:44 PM
Data Sourced
via MITRE·03:44 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2023-53596?

CVE-2023-53596 has been classified with a severity that addresses resource management issues in device unregistering.

2

How do I fix CVE-2023-53596?

To fix CVE-2023-53596, update your Linux kernel to the latest version that incorporates the necessary patches.

3

What systems are affected by CVE-2023-53596?

CVE-2023-53596 affects the Linux kernel, specifically in scenarios involving bus-less device management.

4

What vulnerabilities are related to device resources in CVE-2023-53596?

CVE-2023-53596 highlights issues with devm resource management when unregistering devices in the Linux kernel.

5

Is CVE-2023-53596 a critical vulnerability?

While CVE-2023-53596 addresses important resource management, the criticality depends on the specific use case and environment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203