CVE-2022-48812

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: 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.

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/0d120dfb5d67edc5bcd1804e167dba2b30809afd
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/2443ba2fe396bdde187a2fdfa6a57375643ae93c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b5652bc50dde7b84e93dfb25479b64b817e377c1
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e177d2e85ebcd3008c4b2abc293f4118e04eedef
    Patch

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/0d120dfb5d67edc5bcd1804e167dba2b30809afd
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/2443ba2fe396bdde187a2fdfa6a57375643ae93c
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b5652bc50dde7b84e93dfb25479b64b817e377c1
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/e177d2e85ebcd3008c4b2abc293f4118e04eedef
    Patch