CVE-2022-50624
In the Linux kernel, the following vulnerability has been resolved: net: netsec: fix error handling in netsec_register_mdio() If phy_device_register() fails, phy_device_free() need be called to put refcount, so memory of phy device and device name can be freed in callback function. If get_phy_device() fails, mdiobus_unregister() need be called, or it will cause warning in mdiobus_free() and kobject is leaked.
Affected versions
Linux kernel versions
4.16
and later are affected. Fixed in
4.19.264,
5.4.223,
5.10.153,
5.15.77,
6.0.7,
6.1
and their respective stable series.
References
The following references provide additional information about CVE-2022-50624 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/1e0bee973ef6fc3c1e3acb014515eaea37c8fa17
-
PatchKernel patch commithttps://git.kernel.org/stable/c/62f0a08e82a6312efd7df7f595c0b11d4ffde610
-
PatchKernel patch commithttps://git.kernel.org/stable/c/728884b22d83148a330b23f9472f1e118b589211
Frequently asked questions
-
What is CVE-2022-50624?
CVE-2022-50624 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.16 onward and has been patched in 4.19.264, 5.4.223, 5.10.153 and others. CVE-2022-50624 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2022-50624?
Yes — CVE-2022-50624 has been patched. Fixed versions include 4.19.264, 5.4.223, 5.10.153 and others. If you are running Linux kernel 4.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-50624 actively exploited?
No — CVE-2022-50624 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.