CVE-2023-54015
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.
Affected versions
Linux kernel versions
5.0
and later are affected. Fixed in
5.4.244,
5.10.181,
5.15.114,
6.1.31,
6.3.5,
6.4
and their respective stable series.
References
The following references provide additional information about CVE-2023-54015 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/1e755065368000205e6683fa924b2654e99f573b
-
PatchKernel patch commithttps://git.kernel.org/stable/c/3dfc1004d9afbf689087ae1eafd88f55481984c7
-
PatchKernel patch commithttps://git.kernel.org/stable/c/a3a516caef2c5be2f4d171890a8b3415bfab4e5e
Frequently asked questions
-
What is CVE-2023-54015?
CVE-2023-54015 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.0 onward and has been patched in 5.4.244, 5.10.181, 5.15.114 and others. CVE-2023-54015 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2023-54015?
Yes — CVE-2023-54015 has been patched. Fixed versions include 5.4.244, 5.10.181, 5.15.114 and others. If you are running Linux kernel 5.0 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2023-54015 actively exploited?
No — CVE-2023-54015 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.