CVE-2024-26756
Vulnerability from cvelistv5
Published
2024-04-03 17:00
Modified
2024-12-19 08:46
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: md: Don't register sync_thread for reshape directly Currently, if reshape is interrupted, then reassemble the array will register sync_thread directly from pers->run(), in this case 'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee that md_do_sync() will be executed, hence stop_sync_thread() will hang because 'MD_RECOVERY_RUNNING' can't be cleared. Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE, however, following hang can still be triggered by dm-raid test shell/lvconvert-raid-reshape.sh occasionally: [root@fedora ~]# cat /proc/1982/stack [<0>] stop_sync_thread+0x1ab/0x270 [md_mod] [<0>] md_frozen_sync_thread+0x5c/0xa0 [md_mod] [<0>] raid_presuspend+0x1e/0x70 [dm_raid] [<0>] dm_table_presuspend_targets+0x40/0xb0 [dm_mod] [<0>] __dm_destroy+0x2a5/0x310 [dm_mod] [<0>] dm_destroy+0x16/0x30 [dm_mod] [<0>] dev_remove+0x165/0x290 [dm_mod] [<0>] ctl_ioctl+0x4bb/0x7b0 [dm_mod] [<0>] dm_ctl_ioctl+0x11/0x20 [dm_mod] [<0>] vfs_ioctl+0x21/0x60 [<0>] __x64_sys_ioctl+0xb9/0xe0 [<0>] do_syscall_64+0xc6/0x230 [<0>] entry_SYSCALL_64_after_hwframe+0x6c/0x74 Meanwhile mddev->recovery is: MD_RECOVERY_RUNNING | MD_RECOVERY_INTR | MD_RECOVERY_RESHAPE | MD_RECOVERY_FROZEN Fix this problem by remove the code to register sync_thread directly from raid10 and raid5. And let md_check_recovery() to register sync_thread.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/13b520fb62b772e408f9b79c5fe18ad414e90417
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ad39c08186f8a0f221337985036ba86731d6aafe
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/13b520fb62b772e408f9b79c5fe18ad414e90417
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/ad39c08186f8a0f221337985036ba86731d6aafe
Impacted products
Vendor Product Version
Linux Linux Version: 2.6.17
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-26756",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-06-17T19:28:01.094375Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-17T19:28:07.779Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T00:14:13.242Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/13b520fb62b772e408f9b79c5fe18ad414e90417"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/ad39c08186f8a0f221337985036ba86731d6aafe"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/md/md.c",
            "drivers/md/raid10.c",
            "drivers/md/raid5.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "13b520fb62b772e408f9b79c5fe18ad414e90417",
              "status": "affected",
              "version": "f67055780caac6a99f43834795c43acf99eba6a6",
              "versionType": "git"
            },
            {
              "lessThan": "ad39c08186f8a0f221337985036ba86731d6aafe",
              "status": "affected",
              "version": "f67055780caac6a99f43834795c43acf99eba6a6",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/md/md.c",
            "drivers/md/raid10.c",
            "drivers/md/raid5.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.17"
            },
            {
              "lessThan": "2.6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.7.*",
              "status": "unaffected",
              "version": "6.7.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.8",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmd: Don\u0027t register sync_thread for reshape directly\n\nCurrently, if reshape is interrupted, then reassemble the array will\nregister sync_thread directly from pers-\u003erun(), in this case\n\u0027MD_RECOVERY_RUNNING\u0027 is set directly, however, there is no guarantee\nthat md_do_sync() will be executed, hence stop_sync_thread() will hang\nbecause \u0027MD_RECOVERY_RUNNING\u0027 can\u0027t be cleared.\n\nLast patch make sure that md_do_sync() will set MD_RECOVERY_DONE,\nhowever, following hang can still be triggered by dm-raid test\nshell/lvconvert-raid-reshape.sh occasionally:\n\n[root@fedora ~]# cat /proc/1982/stack\n[\u003c0\u003e] stop_sync_thread+0x1ab/0x270 [md_mod]\n[\u003c0\u003e] md_frozen_sync_thread+0x5c/0xa0 [md_mod]\n[\u003c0\u003e] raid_presuspend+0x1e/0x70 [dm_raid]\n[\u003c0\u003e] dm_table_presuspend_targets+0x40/0xb0 [dm_mod]\n[\u003c0\u003e] __dm_destroy+0x2a5/0x310 [dm_mod]\n[\u003c0\u003e] dm_destroy+0x16/0x30 [dm_mod]\n[\u003c0\u003e] dev_remove+0x165/0x290 [dm_mod]\n[\u003c0\u003e] ctl_ioctl+0x4bb/0x7b0 [dm_mod]\n[\u003c0\u003e] dm_ctl_ioctl+0x11/0x20 [dm_mod]\n[\u003c0\u003e] vfs_ioctl+0x21/0x60\n[\u003c0\u003e] __x64_sys_ioctl+0xb9/0xe0\n[\u003c0\u003e] do_syscall_64+0xc6/0x230\n[\u003c0\u003e] entry_SYSCALL_64_after_hwframe+0x6c/0x74\n\nMeanwhile mddev-\u003erecovery is:\nMD_RECOVERY_RUNNING |\nMD_RECOVERY_INTR |\nMD_RECOVERY_RESHAPE |\nMD_RECOVERY_FROZEN\n\nFix this problem by remove the code to register sync_thread directly\nfrom raid10 and raid5. And let md_check_recovery() to register\nsync_thread."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-12-19T08:46:34.016Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/13b520fb62b772e408f9b79c5fe18ad414e90417"
        },
        {
          "url": "https://git.kernel.org/stable/c/ad39c08186f8a0f221337985036ba86731d6aafe"
        }
      ],
      "title": "md: Don\u0027t register sync_thread for reshape directly",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-26756",
    "datePublished": "2024-04-03T17:00:40.814Z",
    "dateReserved": "2024-02-19T14:20:24.170Z",
    "dateUpdated": "2024-12-19T08:46:34.016Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-26756\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-04-03T17:15:52.150\",\"lastModified\":\"2024-11-21T09:03:00.037\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmd: Don\u0027t register sync_thread for reshape directly\\n\\nCurrently, if reshape is interrupted, then reassemble the array will\\nregister sync_thread directly from pers-\u003erun(), in this case\\n\u0027MD_RECOVERY_RUNNING\u0027 is set directly, however, there is no guarantee\\nthat md_do_sync() will be executed, hence stop_sync_thread() will hang\\nbecause \u0027MD_RECOVERY_RUNNING\u0027 can\u0027t be cleared.\\n\\nLast patch make sure that md_do_sync() will set MD_RECOVERY_DONE,\\nhowever, following hang can still be triggered by dm-raid test\\nshell/lvconvert-raid-reshape.sh occasionally:\\n\\n[root@fedora ~]# cat /proc/1982/stack\\n[\u003c0\u003e] stop_sync_thread+0x1ab/0x270 [md_mod]\\n[\u003c0\u003e] md_frozen_sync_thread+0x5c/0xa0 [md_mod]\\n[\u003c0\u003e] raid_presuspend+0x1e/0x70 [dm_raid]\\n[\u003c0\u003e] dm_table_presuspend_targets+0x40/0xb0 [dm_mod]\\n[\u003c0\u003e] __dm_destroy+0x2a5/0x310 [dm_mod]\\n[\u003c0\u003e] dm_destroy+0x16/0x30 [dm_mod]\\n[\u003c0\u003e] dev_remove+0x165/0x290 [dm_mod]\\n[\u003c0\u003e] ctl_ioctl+0x4bb/0x7b0 [dm_mod]\\n[\u003c0\u003e] dm_ctl_ioctl+0x11/0x20 [dm_mod]\\n[\u003c0\u003e] vfs_ioctl+0x21/0x60\\n[\u003c0\u003e] __x64_sys_ioctl+0xb9/0xe0\\n[\u003c0\u003e] do_syscall_64+0xc6/0x230\\n[\u003c0\u003e] entry_SYSCALL_64_after_hwframe+0x6c/0x74\\n\\nMeanwhile mddev-\u003erecovery is:\\nMD_RECOVERY_RUNNING |\\nMD_RECOVERY_INTR |\\nMD_RECOVERY_RESHAPE |\\nMD_RECOVERY_FROZEN\\n\\nFix this problem by remove the code to register sync_thread directly\\nfrom raid10 and raid5. And let md_check_recovery() to register\\nsync_thread.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: md: No registre sync_thread para remodelar directamente Actualmente, si se interrumpe el proceso de remodelaci\u00f3n, volver a ensamblar la matriz registrar\u00e1 sync_thread directamente desde pers-\u0026gt;run(), en este caso \u0027MD_RECOVERY_RUNNING \u0027 se configura directamente, sin embargo, no hay garant\u00eda de que md_do_sync() se ejecute, por lo tanto, stop_sync_thread() se bloquear\u00e1 porque \u0027MD_RECOVERY_RUNNING\u0027 no se puede borrar. En el \u00faltimo parche, aseg\u00farese de que md_do_sync() establezca MD_RECOVERY_DONE; sin embargo, dm-raid test shell/lvconvert-raid-reshape.sh ocasionalmente puede activar el siguiente bloqueo: [root@fedora ~]# cat /proc/1982/stack [\u0026lt;0\u0026gt;] stop_sync_thread+0x1ab/0x270 [md_mod] [\u0026lt;0\u0026gt;] md_frozen_sync_thread+0x5c/0xa0 [md_mod] [\u0026lt;0\u0026gt;] raid_presuspend+0x1e/0x70 [dm_raid] [\u0026lt;0\u0026gt;] dm_table_presuspend_targets+0x40/0xb0 [ dm_mod] [\u0026lt;0\u0026gt;] __dm_destroy+0x2a5/0x310 [dm_mod] [\u0026lt;0\u0026gt;] dm_destroy+0x16/0x30 [dm_mod] [\u0026lt;0\u0026gt;] dev_remove+0x165/0x290 [dm_mod] [\u0026lt;0\u0026gt;] ctl_ioctl+0x4bb/ 0x7b0 [dm_mod] [\u0026lt;0\u0026gt;] dm_ctl_ioctl+0x11/0x20 [dm_mod] [\u0026lt;0\u0026gt;] vfs_ioctl+0x21/0x60 [\u0026lt;0\u0026gt;] __x64_sys_ioctl+0xb9/0xe0 [\u0026lt;0\u0026gt;] do_syscall_64+0xc6/0x230 [\u0026lt;0 \u0026gt;] Entry_SYSCALL_64_after_hwframe+0x6c/0x74 Mientras tanto mddev-\u0026gt;recovery es: MD_RECOVERY_RUNNING | MD_RECOVERY_INTR | MD_RECOVERY_RESHAPE | MD_RECOVERY_FROZEN Solucione este problema eliminando el c\u00f3digo para registrar sync_thread directamente desde raid10 y raid5. Y deje que md_check_recovery() registre sync_thread.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/13b520fb62b772e408f9b79c5fe18ad414e90417\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/ad39c08186f8a0f221337985036ba86731d6aafe\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/13b520fb62b772e408f9b79c5fe18ad414e90417\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/ad39c08186f8a0f221337985036ba86731d6aafe\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}"
  }
}


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.