CVE-2023-53849
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-12-09

Last updated on: 2025-12-09

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm: fix workqueue leak on bind errors Make sure to destroy the workqueue also in case of early errors during bind (e.g. a subcomponent failing to bind). Since commit c3b790ea07a1 ("drm: Manage drm_mode_config_init with drmm_") the mode config will be freed when the drm device is released also when using the legacy interface, but add an explicit cleanup for consistency and to facilitate backporting. Patchwork: https://patchwork.freedesktop.org/patch/525093/
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-09
Last Modified
2025-12-09
Generated
2026-05-07
AI Q&A
2025-12-09
EPSS Evaluated
2026-05-05
NVD
CVE-2023-53849
EUVD
EUVD-2023-60147
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a workqueue leak in the Linux kernel's drm/msm component that occurs on bind errors. Specifically, when there are early errors during the binding process of a subcomponent, the workqueue is not properly destroyed, leading to a resource leak. The fix ensures that the workqueue is explicitly destroyed even if binding fails early.


How can this vulnerability impact me? :

The impact of this vulnerability is a resource leak in the Linux kernel, which could lead to increased memory usage or system instability over time if the workqueue is not properly cleaned up during bind errors.


What immediate steps should I take to mitigate this vulnerability?

Apply the patch that fixes the workqueue leak in the drm/msm component of the Linux kernel. This involves updating the kernel to a version that includes the fix for the workqueue leak on bind errors as described in the patchwork link: https://patchwork.freedesktop.org/patch/525093/. Ensuring your system is running an updated kernel version that includes this fix is the immediate mitigation step.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart