Strix
26.1K

CVE-2023-54015

UnknownEPSS 0.17%

Last modified

CVE-2023-54015 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

7.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= fadd59fc50d010145f251db583c7ccef37393d19, < 3dfc1004d9afbf689087ae1eafd88f55481984c7; >= fadd59fc50d010145f251db583c7ccef37393d19, < d4d10a6df1529b3f446cdada5c25e065f4712756; >= fadd59fc50d010145f251db583c7ccef37393d19, < 1e755065368000205e6683fa924b2654e99f573b; >= fadd59fc50d010145f251db583c7ccef37393d19, < eaa365c10459052cbe3e44caa4ad760cb93bd435; >= fadd59fc50d010145f251db583c7ccef37393d19, < a3a516caef2c5be2f4d171890a8b3415bfab4e5e; >= fadd59fc50d010145f251db583c7ccef37393d19, < af87194352cad882d787d06fb7efa714acd95427
LinuxLinux5.0

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is 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.
How severe is CVE-2023-54015?
Severity scoring for CVE-2023-54015 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2023-54015?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2023

View all 2023CVEs →

Are you affected by CVE-2023-54015?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST