CVE-2023-54324
Unknown Unknown - Not Provided
Use-After-Free Race Condition in Linux Kernel Multipath Device Manager

Publication date: 2025-12-30

Last updated on: 2025-12-30

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: dm: fix a race condition in retrieve_deps There's a race condition in the multipath target when retrieve_deps races with multipath_message calling dm_get_device and dm_put_device. retrieve_deps walks the list of open devices without holding any lock but multipath may add or remove devices to the list while it is running. The end result may be memory corruption or use-after-free memory access. See this description of a UAF with multipath_message(): https://listman.redhat.com/archives/dm-devel/2022-October/052373.html Fix this bug by introducing a new rw semaphore "devices_lock". We grab devices_lock for read in retrieve_deps and we grab it for write in dm_get_device and dm_put_device.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-30
Last Modified
2025-12-30
Generated
2026-05-06
AI Q&A
2025-12-30
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux kernel *
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 race condition in the Linux kernel's device mapper multipath target. Specifically, the function retrieve_deps accesses a list of open devices without holding a lock, while other functions (multipath_message calling dm_get_device and dm_put_device) may concurrently add or remove devices from that list. This can lead to memory corruption or use-after-free (UAF) errors because the list is modified while being read. The issue was fixed by introducing a new read-write semaphore called devices_lock to properly synchronize access to the device list.


How can this vulnerability impact me? :

This vulnerability can cause memory corruption or use-after-free conditions in the Linux kernel's multipath device mapper. Such memory errors can lead to system instability, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service by exploiting the race condition.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update the Linux kernel to a version that includes the fix for the race condition in retrieve_deps. The fix involves introducing a new rw semaphore "devices_lock" to properly synchronize access to the list of open devices, preventing memory corruption or use-after-free errors.


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