Strix
26.1K

CVE-2022-50624

UnknownEPSS 0.17%

Last modified

CVE-2022-50624 is a vulnerability of currently unknown severity. 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.. 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: 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.

Metrics

EPSS Probability
0.17%

6.9th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

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

VendorProductVersions
LinuxLinux>= 533dd11a12f698c571a12271b20f235792d3e148, < 728884b22d83148a330b23f9472f1e118b589211; >= 533dd11a12f698c571a12271b20f235792d3e148, < fda2d07234a21be4d71ebfe97a45f499726902d6; >= 533dd11a12f698c571a12271b20f235792d3e148, < 62f0a08e82a6312efd7df7f595c0b11d4ffde610; >= 533dd11a12f698c571a12271b20f235792d3e148, < 1e0bee973ef6fc3c1e3acb014515eaea37c8fa17; >= 533dd11a12f698c571a12271b20f235792d3e148, < 846e677daf51220d7975c61a20e440a88473951e; >= 533dd11a12f698c571a12271b20f235792d3e148, < 94423589689124e8cd145b38a1034be7f25835b2
LinuxLinux4.16

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is 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.
How severe is CVE-2022-50624?
Severity scoring for CVE-2022-50624 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2022-50624?
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 2022

View all 2022CVEs →

Are you affected by CVE-2022-50624?

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

Scan your code now

Source: NVD / NIST