CVE-2022-48815

published 16 Jul 2024 · updated 11 May 2026

net: dsa: bcm_sf2: 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 08e1a3554e99a1a5bd2835907381e2383ee85cae, Kernel 08f1a20822349004bb9cc1b153ecb516e9f2889d, Kernel 2770b795294ed312375c11ef1d0b810499c66b83 and 1 more.

In the Linux kernel, the following vulnerability has been resolved: net: dsa: bcm_sf2: 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 Starfighter 2 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 bcm_sf2 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 bcm_sf2 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 <08e1a3554e99a1a5bd2835907381e2383ee85cae, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <08f1a20822349004bb9cc1b153ecb516e9f2889d, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <2770b795294ed312375c11ef1d0b810499c66b83, >=ac3a68d56651c3dad2c12c7afce065fe15267f44 <caabb5f64f5c32fceed93356bb688ef1ec6c578308e1a3554e99a1a5bd2835907381e2383ee85cae, 08f1a20822349004bb9cc1b153ecb516e9f2889d, 2770b795294ed312375c11ef1d0b810499c66b83, caabb5f64f5c32fceed93356bb688ef1ec6c5783

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-48815 severity on Zeptric[![CVE-2022-48815](https://zeptric.io/badge/cve/CVE-2022-48815.svg)](https://zeptric.io/cve/CVE-2022-48815)