Skip to content
Heist/ feed
Back to feed
UnratedFix available

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

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.10.101, 5.15.24, 5.16.10
CVEs
CVE-2022-48815
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 02:59 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 16 Jul 2024, 11:44 UTC

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.

osv:CVE-2022-48815

Kernel

Fixed versions: 5.10.101, 5.15.24, 5.16.10

Complete source record
{
  "id": "02f6632c4cf006553e1b28aba5ec326e8307f0e214ed37594d04c2e5701b98f1",
  "url": "https://osv.dev/vulnerability/CVE-2022-48815",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "net: dsa: bcm_sf2: don't use devres for mdiobus",
    "summary": "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.",
    "evidence": "osv:CVE-2022-48815",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.10.101",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.24",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.16.10",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2022-48815",
      "aliases": [
        "CVE-2022-48815"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ac3a68d56651c3dad2c12c7afce065fe15267f44"
                },
                {
                  "fixed": "2770b795294ed312375c11ef1d0b810499c66b83"
                },
                {
                  "fixed": "caabb5f64f5c32fceed93356bb688ef1ec6c5783"
                },
                {
                  "fixed": "08e1a3554e99a1a5bd2835907381e2383ee85cae"
                },
                {
                  "fixed": "08f1a20822349004bb9cc1b153ecb516e9f2889d"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48815.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.9.0"
                },
                {
                  "fixed": "5.10.101"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.24"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "5.16.10"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48815.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:32.733053443Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/08e1a3554e99a1a5bd2835907381e2383ee85cae",
        "https://git.kernel.org/stable/c/08f1a20822349004bb9cc1b153ecb516e9f2889d",
        "https://git.kernel.org/stable/c/2770b795294ed312375c11ef1d0b810499c66b83",
        "https://git.kernel.org/stable/c/caabb5f64f5c32fceed93356bb688ef1ec6c5783",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48815.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-48815",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48815.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-48815",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 499796,
  "published_at": "2024-07-16T11:44:03.971+00:00"
}