cve-2022-48808
Vulnerability from cvelistv5
Published
2024-07-16 11:43
Modified
2024-12-19 08:08
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: net: dsa: fix panic when DSA master device unbinds on shutdown Rafael reports that on a system with LX2160A and Marvell DSA switches, if a reboot occurs while the DSA master (dpaa2-eth) is up, the following panic can be seen: systemd-shutdown[1]: Rebooting. Unable to handle kernel paging request at virtual address 00a0000800000041 [00a0000800000041] address between user and kernel address ranges Internal error: Oops: 96000004 [#1] PREEMPT SMP CPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32 pc : dsa_slave_netdevice_event+0x130/0x3e4 lr : raw_notifier_call_chain+0x50/0x6c Call trace: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver_internal+0xac/0xb0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 device_for_each_child+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 device_release_driver+0x28/0x40 bus_remove_device+0x118/0x124 device_del+0x174/0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 device_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17c It can be seen from the stack trace that the problem is that the deregistration of the master causes a dev_close(), which gets notified as NETDEV_GOING_DOWN to dsa_slave_netdevice_event(). But dsa_switch_shutdown() has already run, and this has unregistered the DSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to call dev_close_many() on those slave interfaces, leading to the problem. The previous attempt to avoid the NETDEV_GOING_DOWN on the master after dsa_switch_shutdown() was called seems improper. Unregistering the slave interfaces is unnecessary and unhelpful. Instead, after the slaves have stopped being uppers of the DSA master, we can now reset to NULL the master->dsa_ptr pointer, which will make DSA start ignoring all future notifier events on the master.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7Patch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339aePatch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5Patch
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7Patch
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339aePatch
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5Patch
Impacted products
Vendor Product Version
Linux Linux Version: 0650bf52b31ff35dc6430fc2e37969c36baba724
Version: 0650bf52b31ff35dc6430fc2e37969c36baba724
Version: 0650bf52b31ff35dc6430fc2e37969c36baba724
 Create a notification for this product.
   Linux Linux Version: 5.15
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T15:25:01.570Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2022-48808",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-10T16:58:41.309818Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-11T17:34:13.530Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/dsa/dsa2.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "ff45899e732e57088985e3a497b1d9100571c0f5",
              "status": "affected",
              "version": "0650bf52b31ff35dc6430fc2e37969c36baba724",
              "versionType": "git"
            },
            {
              "lessThan": "89b60402d43cdab4387dbbf24afebda5cf092ae7",
              "status": "affected",
              "version": "0650bf52b31ff35dc6430fc2e37969c36baba724",
              "versionType": "git"
            },
            {
              "lessThan": "ee534378f00561207656663d93907583958339ae",
              "status": "affected",
              "version": "0650bf52b31ff35dc6430fc2e37969c36baba724",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/dsa/dsa2.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.15"
            },
            {
              "lessThan": "5.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.155",
              "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: fix panic when DSA master device unbinds on shutdown\n\nRafael reports that on a system with LX2160A and Marvell DSA switches,\nif a reboot occurs while the DSA master (dpaa2-eth) is up, the following\npanic can be seen:\n\nsystemd-shutdown[1]: Rebooting.\nUnable to handle kernel paging request at virtual address 00a0000800000041\n[00a0000800000041] address between user and kernel address ranges\nInternal error: Oops: 96000004 [#1] PREEMPT SMP\nCPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32\npc : dsa_slave_netdevice_event+0x130/0x3e4\nlr : raw_notifier_call_chain+0x50/0x6c\nCall trace:\n dsa_slave_netdevice_event+0x130/0x3e4\n raw_notifier_call_chain+0x50/0x6c\n call_netdevice_notifiers_info+0x54/0xa0\n __dev_close_many+0x50/0x130\n dev_close_many+0x84/0x120\n unregister_netdevice_many+0x130/0x710\n unregister_netdevice_queue+0x8c/0xd0\n unregister_netdev+0x20/0x30\n dpaa2_eth_remove+0x68/0x190\n fsl_mc_driver_remove+0x20/0x5c\n __device_release_driver+0x21c/0x220\n device_release_driver_internal+0xac/0xb0\n device_links_unbind_consumers+0xd4/0x100\n __device_release_driver+0x94/0x220\n device_release_driver+0x28/0x40\n bus_remove_device+0x118/0x124\n device_del+0x174/0x420\n fsl_mc_device_remove+0x24/0x40\n __fsl_mc_device_remove+0xc/0x20\n device_for_each_child+0x58/0xa0\n dprc_remove+0x90/0xb0\n fsl_mc_driver_remove+0x20/0x5c\n __device_release_driver+0x21c/0x220\n device_release_driver+0x28/0x40\n bus_remove_device+0x118/0x124\n device_del+0x174/0x420\n fsl_mc_bus_remove+0x80/0x100\n fsl_mc_bus_shutdown+0xc/0x1c\n platform_shutdown+0x20/0x30\n device_shutdown+0x154/0x330\n __do_sys_reboot+0x1cc/0x250\n __arm64_sys_reboot+0x20/0x30\n invoke_syscall.constprop.0+0x4c/0xe0\n do_el0_svc+0x4c/0x150\n el0_svc+0x24/0xb0\n el0t_64_sync_handler+0xa8/0xb0\n el0t_64_sync+0x178/0x17c\n\nIt can be seen from the stack trace that the problem is that the\nderegistration of the master causes a dev_close(), which gets notified\nas NETDEV_GOING_DOWN to dsa_slave_netdevice_event().\nBut dsa_switch_shutdown() has already run, and this has unregistered the\nDSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to\ncall dev_close_many() on those slave interfaces, leading to the problem.\n\nThe previous attempt to avoid the NETDEV_GOING_DOWN on the master after\ndsa_switch_shutdown() was called seems improper. Unregistering the slave\ninterfaces is unnecessary and unhelpful. Instead, after the slaves have\nstopped being uppers of the DSA master, we can now reset to NULL the\nmaster-\u003edsa_ptr pointer, which will make DSA start ignoring all future\nnotifier events on the master."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-12-19T08:08:07.786Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5"
        },
        {
          "url": "https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7"
        },
        {
          "url": "https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae"
        }
      ],
      "title": "net: dsa: fix panic when DSA master device unbinds on shutdown",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-48808",
    "datePublished": "2024-07-16T11:43:59.089Z",
    "dateReserved": "2024-07-16T11:38:08.896Z",
    "dateUpdated": "2024-12-19T08:08:07.786Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-48808\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-07-16T12:15:05.120\",\"lastModified\":\"2024-11-21T07:34:07.673\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: dsa: fix panic when DSA master device unbinds on shutdown\\n\\nRafael reports that on a system with LX2160A and Marvell DSA switches,\\nif a reboot occurs while the DSA master (dpaa2-eth) is up, the following\\npanic can be seen:\\n\\nsystemd-shutdown[1]: Rebooting.\\nUnable to handle kernel paging request at virtual address 00a0000800000041\\n[00a0000800000041] address between user and kernel address ranges\\nInternal error: Oops: 96000004 [#1] PREEMPT SMP\\nCPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32\\npc : dsa_slave_netdevice_event+0x130/0x3e4\\nlr : raw_notifier_call_chain+0x50/0x6c\\nCall trace:\\n dsa_slave_netdevice_event+0x130/0x3e4\\n raw_notifier_call_chain+0x50/0x6c\\n call_netdevice_notifiers_info+0x54/0xa0\\n __dev_close_many+0x50/0x130\\n dev_close_many+0x84/0x120\\n unregister_netdevice_many+0x130/0x710\\n unregister_netdevice_queue+0x8c/0xd0\\n unregister_netdev+0x20/0x30\\n dpaa2_eth_remove+0x68/0x190\\n fsl_mc_driver_remove+0x20/0x5c\\n __device_release_driver+0x21c/0x220\\n device_release_driver_internal+0xac/0xb0\\n device_links_unbind_consumers+0xd4/0x100\\n __device_release_driver+0x94/0x220\\n device_release_driver+0x28/0x40\\n bus_remove_device+0x118/0x124\\n device_del+0x174/0x420\\n fsl_mc_device_remove+0x24/0x40\\n __fsl_mc_device_remove+0xc/0x20\\n device_for_each_child+0x58/0xa0\\n dprc_remove+0x90/0xb0\\n fsl_mc_driver_remove+0x20/0x5c\\n __device_release_driver+0x21c/0x220\\n device_release_driver+0x28/0x40\\n bus_remove_device+0x118/0x124\\n device_del+0x174/0x420\\n fsl_mc_bus_remove+0x80/0x100\\n fsl_mc_bus_shutdown+0xc/0x1c\\n platform_shutdown+0x20/0x30\\n device_shutdown+0x154/0x330\\n __do_sys_reboot+0x1cc/0x250\\n __arm64_sys_reboot+0x20/0x30\\n invoke_syscall.constprop.0+0x4c/0xe0\\n do_el0_svc+0x4c/0x150\\n el0_svc+0x24/0xb0\\n el0t_64_sync_handler+0xa8/0xb0\\n el0t_64_sync+0x178/0x17c\\n\\nIt can be seen from the stack trace that the problem is that the\\nderegistration of the master causes a dev_close(), which gets notified\\nas NETDEV_GOING_DOWN to dsa_slave_netdevice_event().\\nBut dsa_switch_shutdown() has already run, and this has unregistered the\\nDSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to\\ncall dev_close_many() on those slave interfaces, leading to the problem.\\n\\nThe previous attempt to avoid the NETDEV_GOING_DOWN on the master after\\ndsa_switch_shutdown() was called seems improper. Unregistering the slave\\ninterfaces is unnecessary and unhelpful. Instead, after the slaves have\\nstopped being uppers of the DSA master, we can now reset to NULL the\\nmaster-\u003edsa_ptr pointer, which will make DSA start ignoring all future\\nnotifier events on the master.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: dsa: corrige el p\u00e1nico cuando el dispositivo maestro DSA se desvincula al apagar Rafael informa que en un sistema con conmutadores LX2160A y Marvell DSA, si se produce un reinicio mientras el DSA maestro (dpaa2-eth ) est\u00e1 activo, se puede ver el siguiente p\u00e1nico: systemd-shutdown[1]: Rebooting. No se puede manejar la solicitud de paginaci\u00f3n del kernel en la direcci\u00f3n virtual 00a0000800000041 [00a0000800000041] direcci\u00f3n entre los rangos de direcciones del usuario y del kernel Error interno: Ups: 96000004 [#1] CPU SMP PREEMPT: 6 PID: 1 Comm: systemd-shutdow No est\u00e1 contaminado 5.16.5-00042 -g8f5585009b24 #32 pc: dsa_slave_netdevice_event+0x130/0x3e4 lr: raw_notifier_call_chain+0x50/0x6c Rastreo de llamadas: dsa_slave_netdevice_event+0x130/0x3e4 raw_notifier_call_chain+0x50/0x6c call_netdevice_notifiers_info+ 0x54/0xa0 __dev_close_many+0x50/0x130 dev_close_many+0x84/0x120 unregister_netdevice_many+0x130/ 0x710 unregister_netdevice_queue+0x8c/0xd0 unregister_netdev+0x20/0x30 dpaa2_eth_remove+0x68/0x190 fsl_mc_driver_remove+0x20/0x5c __device_release_driver+0x21c/0x220 dispositivo_release_driver_internal+0xac/0x b0 device_links_unbind_consumers+0xd4/0x100 __device_release_driver+0x94/0x220 dispositivo_release_driver+0x28/0x40 bus_remove_device+0x118/ 0x124 dispositivo_del+0x174/0x420 fsl_mc_device_remove+0x24/0x40 __fsl_mc_device_remove+0xc/0x20 dispositivo_para_cada_ni\u00f1o+0x58/0xa0 dprc_remove+0x90/0xb0 fsl_mc_driver_remove+0x20/0x5c __ dispositivo_liberaci\u00f3n_controlador+0x21c/0x220 dispositivo_liberaci\u00f3n_controlador+0x28/0x40 bus_remove_device+0x118/0x124 dispositivo_del+0x174/ 0x420 fsl_mc_bus_remove+0x80/0x100 fsl_mc_bus_shutdown+0xc/0x1c platform_shutdown+0x20/0x30 dispositivo_shutdown+0x154/0x330 __do_sys_reboot+0x1cc/0x250 __arm64_sys_reboot+0x20/0x30 invoke_syscall.constprop.0+0x4c/0xe0 do_el0_svc+0x4c/0x150 el0_svc+0x24/0xb0 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x178/0x17c Se puede ver en el seguimiento de la pila que el problema es que la cancelaci\u00f3n del registro del maestro provoca un dev_close(), que se notifica como NETDEV_GOING_DOWN a dsa_slave_netdevice_event(). Pero dsa_switch_shutdown() ya se ejecut\u00f3, y esto anul\u00f3 el registro de las interfaces esclavas DSA y, a\u00fan as\u00ed, el controlador NETDEV_GOING_DOWN intenta llamar a dev_close_many() en esas interfaces esclavas, lo que genera el problema. El intento anterior de evitar NETDEV_GOING_DOWN en el maestro despu\u00e9s de llamar a dsa_switch_shutdown() parece inadecuado. Anular el registro de las interfaces esclavas es innecesario e in\u00fatil. En cambio, despu\u00e9s de que los esclavos hayan dejado de ser superiores al maestro DSA, ahora podemos restablecer a NULL el puntero maestro-\u0026gt;dsa_ptr, lo que har\u00e1 que DSA comience a ignorar todos los eventos notificadores futuros en el maestro.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.15\",\"versionEndExcluding\":\"5.15.155\",\"matchCriteriaId\":\"5EA785B4-F15F-4577-975F-43739EC89827\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"5.16.10\",\"matchCriteriaId\":\"679523BA-1392-404B-AB85-F5A5408B1ECC\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-03T15:25:01.570Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-48808\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-10T16:58:41.309818Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-11T12:42:21.465Z\"}}], \"cna\": {\"title\": \"net: dsa: fix panic when DSA master device unbinds on shutdown\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"0650bf52b31ff35dc6430fc2e37969c36baba724\", \"lessThan\": \"ff45899e732e57088985e3a497b1d9100571c0f5\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0650bf52b31ff35dc6430fc2e37969c36baba724\", \"lessThan\": \"89b60402d43cdab4387dbbf24afebda5cf092ae7\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0650bf52b31ff35dc6430fc2e37969c36baba724\", \"lessThan\": \"ee534378f00561207656663d93907583958339ae\", \"versionType\": \"git\"}], \"programFiles\": [\"net/dsa/dsa2.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.15\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.15\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.155\", \"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\": [\"net/dsa/dsa2.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/ff45899e732e57088985e3a497b1d9100571c0f5\"}, {\"url\": \"https://git.kernel.org/stable/c/89b60402d43cdab4387dbbf24afebda5cf092ae7\"}, {\"url\": \"https://git.kernel.org/stable/c/ee534378f00561207656663d93907583958339ae\"}], \"x_generator\": {\"engine\": \"bippy-5f407fcff5a0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet: dsa: fix panic when DSA master device unbinds on shutdown\\n\\nRafael reports that on a system with LX2160A and Marvell DSA switches,\\nif a reboot occurs while the DSA master (dpaa2-eth) is up, the following\\npanic can be seen:\\n\\nsystemd-shutdown[1]: Rebooting.\\nUnable to handle kernel paging request at virtual address 00a0000800000041\\n[00a0000800000041] address between user and kernel address ranges\\nInternal error: Oops: 96000004 [#1] PREEMPT SMP\\nCPU: 6 PID: 1 Comm: systemd-shutdow Not tainted 5.16.5-00042-g8f5585009b24 #32\\npc : dsa_slave_netdevice_event+0x130/0x3e4\\nlr : raw_notifier_call_chain+0x50/0x6c\\nCall trace:\\n dsa_slave_netdevice_event+0x130/0x3e4\\n raw_notifier_call_chain+0x50/0x6c\\n call_netdevice_notifiers_info+0x54/0xa0\\n __dev_close_many+0x50/0x130\\n dev_close_many+0x84/0x120\\n unregister_netdevice_many+0x130/0x710\\n unregister_netdevice_queue+0x8c/0xd0\\n unregister_netdev+0x20/0x30\\n dpaa2_eth_remove+0x68/0x190\\n fsl_mc_driver_remove+0x20/0x5c\\n __device_release_driver+0x21c/0x220\\n device_release_driver_internal+0xac/0xb0\\n device_links_unbind_consumers+0xd4/0x100\\n __device_release_driver+0x94/0x220\\n device_release_driver+0x28/0x40\\n bus_remove_device+0x118/0x124\\n device_del+0x174/0x420\\n fsl_mc_device_remove+0x24/0x40\\n __fsl_mc_device_remove+0xc/0x20\\n device_for_each_child+0x58/0xa0\\n dprc_remove+0x90/0xb0\\n fsl_mc_driver_remove+0x20/0x5c\\n __device_release_driver+0x21c/0x220\\n device_release_driver+0x28/0x40\\n bus_remove_device+0x118/0x124\\n device_del+0x174/0x420\\n fsl_mc_bus_remove+0x80/0x100\\n fsl_mc_bus_shutdown+0xc/0x1c\\n platform_shutdown+0x20/0x30\\n device_shutdown+0x154/0x330\\n __do_sys_reboot+0x1cc/0x250\\n __arm64_sys_reboot+0x20/0x30\\n invoke_syscall.constprop.0+0x4c/0xe0\\n do_el0_svc+0x4c/0x150\\n el0_svc+0x24/0xb0\\n el0t_64_sync_handler+0xa8/0xb0\\n el0t_64_sync+0x178/0x17c\\n\\nIt can be seen from the stack trace that the problem is that the\\nderegistration of the master causes a dev_close(), which gets notified\\nas NETDEV_GOING_DOWN to dsa_slave_netdevice_event().\\nBut dsa_switch_shutdown() has already run, and this has unregistered the\\nDSA slave interfaces, and yet, the NETDEV_GOING_DOWN handler attempts to\\ncall dev_close_many() on those slave interfaces, leading to the problem.\\n\\nThe previous attempt to avoid the NETDEV_GOING_DOWN on the master after\\ndsa_switch_shutdown() was called seems improper. Unregistering the slave\\ninterfaces is unnecessary and unhelpful. Instead, after the slaves have\\nstopped being uppers of the DSA master, we can now reset to NULL the\\nmaster-\u003edsa_ptr pointer, which will make DSA start ignoring all future\\nnotifier events on the master.\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-12-19T08:08:07.786Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2022-48808\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-12-19T08:08:07.786Z\", \"dateReserved\": \"2024-07-16T11:38:08.896Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-07-16T11:43:59.089Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}


Log in or create an account to share your comment.




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.