CVE-2022-48815

MEDIUM EPSS 18.4%
Published Jul 16, 20241y ago · Modified Jun 17, 20262w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Jul 16, 2024 1y ago
Last Modified Jun 17, 2026 2w ago

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.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
18.4% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Affected Products 6

VendorProductVersionRange
linuxlinux_kernel*≥5.9  –  <5.10.101
linuxlinux_kernel*≥5.11  –  <5.15.24
linuxlinux_kernel*≥5.16  –  <5.16.10
linuxlinux_kernel5.17any
linuxlinux_kernel5.17any
linuxlinux_kernel5.17any

References 4

  • git.kernel.org https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783
    Patch

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783
    Patch