CVE-2022-48812

published 16 Jul 2024 · updated 11 May 2026

net: dsa: lantiq_gswip: don't use devres for mdiobus

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0d120dfb5d67edc5bcd1804e167dba2b30809afd, Kernel 2443ba2fe396bdde187a2fdfa6a57375643ae93c, Kernel b5652bc50dde7b84e93dfb25479b64b817e377c1 and 1 more.

In the Linux kernel, the following vulnerability has been resolved: net: dsa: lantiq_gswip: don't use devres for mdiobus As explained in commits: 74b6d7d13307 ("net: dsa: realtek: register the MDIO bus under devres") 5135e96a3dd2 ("net: dsa: don't allocate the slave_mii_bus using devres") mdiobus_free() will panic when called from devm_mdiobus_free() <- devres_release_all() <- __device_release_driver(), and that mdiobus was not previously unregistered. The GSWIP switch is a platform device, so the initial set of constraints that I thought would cause this (I2C or SPI buses which call ->remove on ->shutdown) do not apply. But there is one more which applies here. If the DSA master itself is on a bus that calls ->remove from ->shutdown (like dpaa2-eth, which is on the fsl-mc bus), there is a device link between the switch and the DSA master, and device_links_unbind_consumers() will unbind the GSWIP switch driver on shutdown. So the same treatment must be applied to all DSA switch drivers, which is: either use devres for both the mdiobus allocation and registration, or don't use devres at all. The gswip driver has the code structure in place for orderly mdiobus removal, so just replace devm_mdiobus_alloc() with the non-devres variant, and add manual free where necessary, to ensure that we don't let devres free a still-registered bus.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.9, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <0d120dfb5d67edc5bcd1804e167dba2b30809afd, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <2443ba2fe396bdde187a2fdfa6a57375643ae93c, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <b5652bc50dde7b84e93dfb25479b64b817e377c1, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <e177d2e85ebcd3008c4b2abc293f4118e04eedef0d120dfb5d67edc5bcd1804e167dba2b30809afd, 2443ba2fe396bdde187a2fdfa6a57375643ae93c, b5652bc50dde7b84e93dfb25479b64b817e377c1, e177d2e85ebcd3008c4b2abc293f4118e04eedef

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-48812 severity on Zeptric[![CVE-2022-48812](https://zeptric.io/badge/cve/CVE-2022-48812.svg)](https://zeptric.io/cve/CVE-2022-48812)