CVE-2022-48815
net: dsa: bcm_sf2: don't use devres for mdiobus
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.27% · top 81% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected ac3a68d56651c3dad2c12c7afce065fe15267f44 – < 2770b795294ed312375c11ef1d0b810499c66b83
- affected ac3a68d56651c3dad2c12c7afce065fe15267f44 – < caabb5f64f5c32fceed93356bb688ef1ec6c5783
- affected ac3a68d56651c3dad2c12c7afce065fe15267f44 – < 08e1a3554e99a1a5bd2835907381e2383ee85cae
- affected ac3a68d56651c3dad2c12c7afce065fe15267f44 – < 08f1a20822349004bb9cc1b153ecb516e9f2889d
- affected 5.9
- unaffected < 5.9
- unaffected 5.10.101 – ≤ 5.10.*
- unaffected 5.15.24 – ≤ 5.15.*
- unaffected 5.16.10 – ≤ 5.16.*
- unaffected 5.17 – ≤ *
References (4)
- https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-48815)Record last updated .