{"uuid": "bccda528-c730-496c-a425-15b3b425bb2e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-48813", "type": "seen", "source": "https://t.me/cvedetector/944", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2022-48813 - \"AMD Felix PCI Device MDIO Bus Registration Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2022-48813 \nPublished : July 16, 2024, 12:15 p.m. | 43\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnet: dsa: felix: don't use devres for mdiobus  \n  \nAs explained in commits:  \n74b6d7d13307 (\"net: dsa: realtek: register the MDIO bus under devres\")  \n5135e96a3dd2 (\"net: dsa: don't allocate the slave_mii_bus using devres\")  \n  \nmdiobus_free() will panic when called from devm_mdiobus_free() remove on ->shutdown) do not apply. But there is one more which  \napplies here.  \n  \nIf the DSA master itself is on a bus that calls ->remove from ->shutdown  \n(like dpaa2-eth, which is on the fsl-mc bus), there is a device link  \nbetween the switch and the DSA master, and device_links_unbind_consumers()  \nwill unbind the felix switch driver on shutdown.  \n  \nSo the same treatment must be applied to all DSA switch drivers, which  \nis: either use devres for both the mdiobus allocation and registration,  \nor don't use devres at all.  \n  \nThe felix driver has the code structure in place for orderly mdiobus  \nremoval, so just replace devm_mdiobus_alloc_size() with the non-devres  \nvariant, and add manual free where necessary, to ensure that we don't  \nlet devres free a still-registered bus. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-16T15:26:30.000000Z"}