Improper Resource Locking The advisory has been revoked - it doesn't affect any version of package kernel-rt-64k-debug-core (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS9-KERNELRT64KDEBUGCORE-14760788
- published31 Dec 2025
- disclosed30 Dec 2025
Introduced: 30 Dec 2025
CVE-2023-54324 (opens in a new tab)Amendment
The Centos security team deemed this advisory irrelevant for Centos:9.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-64k-debug-core package and not the kernel-rt-64k-debug-core package as distributed by Centos.
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.