CVE-2023-54015
Unknown Unknown - Not Provided
Use-After-Free in Linux mlx5_devcom Device Registration

Publication date: 2025-12-24

Last updated on: 2025-12-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Devcom, fix error flow in mlx5_devcom_register_device In case devcom allocation is failed, mlx5 is always freeing the priv. However, this priv might have been allocated by a different thread, and freeing it might lead to use-after-free bugs. Fix it by freeing the priv only in case it was allocated by the running thread.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-24
Last Modified
2025-12-24
Generated
2026-05-07
AI Q&A
2025-12-24
EPSS Evaluated
2026-05-05
NVD
EUVD
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 in the Linux kernel's mlx5 driver, specifically in the devcom component. When the devcom allocation fails, the code incorrectly frees a private data structure (priv) that might have been allocated by a different thread. This can lead to use-after-free bugs because the memory is freed improperly. The fix ensures that the priv is only freed if it was allocated by the running thread, preventing this unsafe memory operation.


How can this vulnerability impact me? :

The vulnerability can lead to use-after-free bugs in the Linux kernel's mlx5 driver, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges if they can trigger the bug. This impacts system reliability and security.


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 mlx5_devcom_register_device error flow. This fix ensures that the priv is only freed if it was allocated by the running thread, preventing use-after-free bugs.


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