CVE-2023-53596
Description
In the Linux kernel, the following vulnerability has been resolved: drivers: base: Free devm resources when unregistering a device In the current code, devres_release_all() 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 devres_release_all() in the device_del() 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 device_del()") that got reverted by commit a525a3ddeaca ("driver core: free devres in device_release") over memory leaks concerns. This patch effectively combines the two commits mentioned above to release the resources both on device_del() and device_release() and get the best of both worlds.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Linux kernel Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | 6.1.53 |
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
Debian Mixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.5.3-1 |
| sid | Fixed | 6.5.3-1 |
| forky | Fixed | 6.5.3-1 |
| bullseye | Affected | — |
| bookworm | Fixed | 6.1.55-1 |
Red Hat Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| 9 | Fixed | — |
References
- https://access.redhat.com/errata/RHSA-2024:9315
- https://www.suse.com/security/cve/CVE-2023-53596.html
- https://security-tracker.debian.org/tracker/CVE-2023-53596
- https://git.kernel.org/stable/c/297992e5c63528e603666e36081836204fc36ec9
- https://git.kernel.org/stable/c/3bcc4c2a096e8342c8c719e595ce15de212694dd
- https://git.kernel.org/stable/c/699fb50d99039a50e7494de644f96c889279aca3
- https://git.kernel.org/stable/c/83e2ec36a92432e9445e853c12becbbae353b511
- https://git.kernel.org/stable/c/b9ef4b0aa91d2f9f5951faafdbbd47cf01799ec3
- https://git.kernel.org/stable/c/c8c426fae26086a0ca8ab6cc6da2de79810ec038
CWEs
CWE-415
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.