cve-2022-48814
Vulnerability from cvelistv5
Published
2024-07-16 11:44
Modified
2024-12-19 08:08
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: net: dsa: seville: register the mdiobus under devres 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 Seville VSC9959 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 seville 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 seville driver has a code structure that could accommodate both the mdiobus_unregister and mdiobus_free calls, but it has an external dependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls devm_mdiobus_alloc_size() on its behalf. So rather than restructuring that, and exporting yet one more symbol mscc_miim_teardown(), let's work with devres and replace of_mdiobus_register with the devres variant. When we use all-devres, we can ensure that devres doesn't free a still-registered bus (it either runs both callbacks, or none).
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b
Impacted products
Vendor Product Version
Linux Linux Version: ac3a68d56651c3dad2c12c7afce065fe15267f44
Version: ac3a68d56651c3dad2c12c7afce065fe15267f44
Version: ac3a68d56651c3dad2c12c7afce065fe15267f44
 Create a notification for this product.
   Linux Linux Version: 5.9
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T15:25:01.621Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b",
               },
            ],
            title: "CVE Program Container",
         },
         {
            metrics: [
               {
                  other: {
                     content: {
                        id: "CVE-2022-48814",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-09-10T16:58:22.016572Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-09-11T17:34:12.849Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "drivers/net/dsa/ocelot/seville_vsc9953.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "1d13e7221035947c62800c9d3d99b4ed570e27e7",
                     status: "affected",
                     version: "ac3a68d56651c3dad2c12c7afce065fe15267f44",
                     versionType: "git",
                  },
                  {
                     lessThan: "0e816362d823cd46c666e64d8bffe329ee22f4cc",
                     status: "affected",
                     version: "ac3a68d56651c3dad2c12c7afce065fe15267f44",
                     versionType: "git",
                  },
                  {
                     lessThan: "bd488afc3b39e045ba71aab472233f2a78726e7b",
                     status: "affected",
                     version: "ac3a68d56651c3dad2c12c7afce065fe15267f44",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "drivers/net/dsa/ocelot/seville_vsc9953.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "5.9",
                  },
                  {
                     lessThan: "5.9",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.15.*",
                     status: "unaffected",
                     version: "5.15.27",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.16.*",
                     status: "unaffected",
                     version: "5.16.10",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "5.17",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: seville: register the mdiobus under devres\n\nAs explained in commits:\n74b6d7d13307 (\"net: dsa: realtek: register the MDIO bus under devres\")\n5135e96a3dd2 (\"net: dsa: don't allocate the slave_mii_bus using devres\")\n\nmdiobus_free() will panic when called from devm_mdiobus_free() <-\ndevres_release_all() <- __device_release_driver(), and that mdiobus was\nnot previously unregistered.\n\nThe Seville VSC9959 switch is a platform device, so the initial set of\nconstraints that I thought would cause this (I2C or SPI buses which call\n->remove on ->shutdown) do not apply. But there is one more which\napplies here.\n\nIf the DSA master itself is on a bus that calls ->remove from ->shutdown\n(like dpaa2-eth, which is on the fsl-mc bus), there is a device link\nbetween the switch and the DSA master, and device_links_unbind_consumers()\nwill unbind the seville switch driver on shutdown.\n\nSo the same treatment must be applied to all DSA switch drivers, which\nis: either use devres for both the mdiobus allocation and registration,\nor don't use devres at all.\n\nThe seville driver has a code structure that could accommodate both the\nmdiobus_unregister and mdiobus_free calls, but it has an external\ndependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls\ndevm_mdiobus_alloc_size() on its behalf. So rather than restructuring\nthat, and exporting yet one more symbol mscc_miim_teardown(), let's work\nwith devres and replace of_mdiobus_register with the devres variant.\nWhen we use all-devres, we can ensure that devres doesn't free a\nstill-registered bus (it either runs both callbacks, or none).",
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-12-19T08:08:14.680Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7",
            },
            {
               url: "https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc",
            },
            {
               url: "https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b",
            },
         ],
         title: "net: dsa: seville: register the mdiobus under devres",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2022-48814",
      datePublished: "2024-07-16T11:44:03.261Z",
      dateReserved: "2024-07-16T11:38:08.899Z",
      dateUpdated: "2024-12-19T08:08:14.680Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2022-48814\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-07-16T12:15:05.563\",\"lastModified\":\"2024-11-21T07:34:08.330\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: dsa: seville: register the mdiobus under devres\\n\\nAs explained in commits:\\n74b6d7d13307 (\\\"net: dsa: realtek: register the MDIO bus under devres\\\")\\n5135e96a3dd2 (\\\"net: dsa: don't allocate the slave_mii_bus using devres\\\")\\n\\nmdiobus_free() will panic when called from devm_mdiobus_free() <-\\ndevres_release_all() <- __device_release_driver(), and that mdiobus was\\nnot previously unregistered.\\n\\nThe Seville VSC9959 switch is a platform device, so the initial set of\\nconstraints that I thought would cause this (I2C or SPI buses which call\\n->remove on ->shutdown) do not apply. But there is one more which\\napplies here.\\n\\nIf the DSA master itself is on a bus that calls ->remove from ->shutdown\\n(like dpaa2-eth, which is on the fsl-mc bus), there is a device link\\nbetween the switch and the DSA master, and device_links_unbind_consumers()\\nwill unbind the seville switch driver on shutdown.\\n\\nSo the same treatment must be applied to all DSA switch drivers, which\\nis: either use devres for both the mdiobus allocation and registration,\\nor don't use devres at all.\\n\\nThe seville driver has a code structure that could accommodate both the\\nmdiobus_unregister and mdiobus_free calls, but it has an external\\ndependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls\\ndevm_mdiobus_alloc_size() on its behalf. So rather than restructuring\\nthat, and exporting yet one more symbol mscc_miim_teardown(), let's work\\nwith devres and replace of_mdiobus_register with the devres variant.\\nWhen we use all-devres, we can ensure that devres doesn't free a\\nstill-registered bus (it either runs both callbacks, or none).\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: net: dsa: seville: registrar el mdiobus bajo devres Como se explica en commits: 74b6d7d13307 (\\\"net: dsa: realtek: registrar el bus MDIO bajo devres\\\") 5135e96a3dd2 (\\\"net: dsa: no asigne el esclavo_mii_bus usando devres\\\") mdiobus_free() entrará en pánico cuando se llame desde devm_mdiobus_free() &lt;- devres_release_all() &lt;- __device_release_driver(), y ese mdiobus no fue anulado previamente. El conmutador Sevilla VSC9959 es un dispositivo de plataforma, por lo que el conjunto inicial de restricciones que pensé que causarían esto (buses I2C o SPI que llaman -&gt;eliminar encendido -&gt;apagar) no se aplican. Pero hay algo más que se aplica aquí. Si el maestro DSA está en un bus que llama -&gt;remove from -&gt;shutdown (como dpaa2-eth, que está en el bus fsl-mc), hay un enlace de dispositivo entre el conmutador y el maestro DSA, y device_links_unbind_consumers( ) desvinculará el controlador del interruptor de Sevilla al apagarlo. Por lo tanto, se debe aplicar el mismo tratamiento a todos los controladores de conmutador DSA, que es: usar devres tanto para la asignación como para el registro de mdiobus, o no usar devres en absoluto. El controlador Sevilla tiene una estructura de código que podría acomodar las llamadas mdiobus_unregister y mdiobus_free, pero tiene una dependencia externa de mscc_miim_setup() de mdio-mscc-miim.c, que llama a devm_mdiobus_alloc_size() en su nombre. Entonces, en lugar de reestructurar eso y exportar un símbolo más mscc_miim_teardown(), trabajemos con devres y reemplacemos of_mdiobus_register con la variante devres. Cuando usamos all-devres, podemos asegurarnos de que devres no libere un bus aún registrado (ejecuta ambas devoluciones de llamada o ninguna).\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-03T15:25:01.621Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-48814\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-10T16:58:22.016572Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-11T12:42:21.396Z\"}}], \"cna\": {\"title\": \"net: dsa: seville: register the mdiobus under devres\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"ac3a68d56651\", \"lessThan\": \"1d13e7221035\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ac3a68d56651\", \"lessThan\": \"0e816362d823\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ac3a68d56651\", \"lessThan\": \"bd488afc3b39\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/net/dsa/ocelot/seville_vsc9953.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.9\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.9\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.27\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"5.16.10\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.16.*\"}, {\"status\": \"unaffected\", \"version\": \"5.17\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/net/dsa/ocelot/seville_vsc9953.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/1d13e7221035947c62800c9d3d99b4ed570e27e7\"}, {\"url\": \"https://git.kernel.org/stable/c/0e816362d823cd46c666e64d8bffe329ee22f4cc\"}, {\"url\": \"https://git.kernel.org/stable/c/bd488afc3b39e045ba71aab472233f2a78726e7b\"}], \"x_generator\": {\"engine\": \"bippy-9e1c9544281a\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: dsa: seville: register the mdiobus under devres\\n\\nAs explained in commits:\\n74b6d7d13307 (\\\"net: dsa: realtek: register the MDIO bus under devres\\\")\\n5135e96a3dd2 (\\\"net: dsa: don't allocate the slave_mii_bus using devres\\\")\\n\\nmdiobus_free() will panic when called from devm_mdiobus_free() <-\\ndevres_release_all() <- __device_release_driver(), and that mdiobus was\\nnot previously unregistered.\\n\\nThe Seville VSC9959 switch is a platform device, so the initial set of\\nconstraints that I thought would cause this (I2C or SPI buses which call\\n->remove on ->shutdown) do not apply. But there is one more which\\napplies here.\\n\\nIf the DSA master itself is on a bus that calls ->remove from ->shutdown\\n(like dpaa2-eth, which is on the fsl-mc bus), there is a device link\\nbetween the switch and the DSA master, and device_links_unbind_consumers()\\nwill unbind the seville switch driver on shutdown.\\n\\nSo the same treatment must be applied to all DSA switch drivers, which\\nis: either use devres for both the mdiobus allocation and registration,\\nor don't use devres at all.\\n\\nThe seville driver has a code structure that could accommodate both the\\nmdiobus_unregister and mdiobus_free calls, but it has an external\\ndependency upon mscc_miim_setup() from mdio-mscc-miim.c, which calls\\ndevm_mdiobus_alloc_size() on its behalf. So rather than restructuring\\nthat, and exporting yet one more symbol mscc_miim_teardown(), let's work\\nwith devres and replace of_mdiobus_register with the devres variant.\\nWhen we use all-devres, we can ensure that devres doesn't free a\\nstill-registered bus (it either runs both callbacks, or none).\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-11-04T12:17:06.111Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2022-48814\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-11-04T12:17:06.111Z\", \"dateReserved\": \"2024-07-16T11:38:08.899Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-07-16T11:44:03.261Z\", \"assignerShortName\": \"Linux\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.