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.
from fadd59fc50d010145f251db583c7ccef37393d19 before 3dfc1004d9afbf689087ae1eafd88f55481984c7; from fadd59fc50d010145f251db583c7ccef37393d19 before d4d10a6df1529b3f446cdada5c25e065f4712756; from fadd59fc50d010145f251db583c7ccef37393d19 before 1e755065368000205e6683fa924b2654e99f573b; from fadd59fc50d010145f251db583c7ccef37393d19 before eaa365c10459052cbe3e44caa4ad760cb93bd435; from fadd59fc50d010145f251db583c7ccef37393d19 before a3a516caef2c5be2f4d171890a8b3415bfab4e5e; from fadd59fc50d010145f251db583c7ccef37393d19 before af87194352cad882d787d06fb7efa714acd95427
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.