CVE-2023-52982 (GCVE-0-2023-52982)
Vulnerability from cvelistv5
Published
2025-03-27 16:43
Modified
2025-05-04 07:46
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: fscache: Use wait_on_bit() to wait for the freeing of relinquished volume The freeing of relinquished volume will wake up the pending volume acquisition by using wake_up_bit(), however it is mismatched with wait_var_event() used in fscache_wait_on_volume_collision() and it will never wake up the waiter in the wait-queue because these two functions operate on different wait-queues. According to the implementation in fscache_wait_on_volume_collision(), if the wake-up of pending acquisition is delayed longer than 20 seconds (e.g., due to the delay of on-demand fd closing), the first wait_var_event_timeout() will timeout and the following wait_var_event() will hang forever as shown below: FS-Cache: Potential volume collision new=00000024 old=00000022 ...... INFO: task mount:1148 blocked for more than 122 seconds. Not tainted 6.1.0-rc6+ #1 task:mount state:D stack:0 pid:1148 ppid:1 Call Trace: <TASK> __schedule+0x2f6/0xb80 schedule+0x67/0xe0 fscache_wait_on_volume_collision.cold+0x80/0x82 __fscache_acquire_volume+0x40d/0x4e0 erofs_fscache_register_volume+0x51/0xe0 [erofs] erofs_fscache_register_fs+0x19c/0x240 [erofs] erofs_fc_fill_super+0x746/0xaf0 [erofs] vfs_get_super+0x7d/0x100 get_tree_nodev+0x16/0x20 erofs_fc_get_tree+0x20/0x30 [erofs] vfs_get_tree+0x24/0xb0 path_mount+0x2fa/0xa90 do_mount+0x7c/0xa0 __x64_sys_mount+0x8b/0xe0 do_syscall_64+0x30/0x60 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Considering that wake_up_bit() is more selective, so fix it by using wait_on_bit() instead of wait_var_event() to wait for the freeing of relinquished volume. In addition because waitqueue_active() is used in wake_up_bit() and clear_bit() doesn't imply any memory barrier, use clear_and_wake_up_bit() to add the missing memory barrier between cursor->flags and waitqueue_active().
References
Impacted products
Vendor Product Version
Linux Linux Version: 62ab63352350e881ae693a8236b35d7d0516c78b
Version: 62ab63352350e881ae693a8236b35d7d0516c78b
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/fscache/volume.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "3be069f42a7b79d3149194f21cdf24bf23864cac",
              "status": "affected",
              "version": "62ab63352350e881ae693a8236b35d7d0516c78b",
              "versionType": "git"
            },
            {
              "lessThan": "8226e37d82f43657da34dd770e2b38f20242ada7",
              "status": "affected",
              "version": "62ab63352350e881ae693a8236b35d7d0516c78b",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/fscache/volume.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.11",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfscache: Use wait_on_bit() to wait for the freeing of relinquished volume\n\nThe freeing of relinquished volume will wake up the pending volume\nacquisition by using wake_up_bit(), however it is mismatched with\nwait_var_event() used in fscache_wait_on_volume_collision() and it will\nnever wake up the waiter in the wait-queue because these two functions\noperate on different wait-queues.\n\nAccording to the implementation in fscache_wait_on_volume_collision(),\nif the wake-up of pending acquisition is delayed longer than 20 seconds\n(e.g., due to the delay of on-demand fd closing), the first\nwait_var_event_timeout() will timeout and the following wait_var_event()\nwill hang forever as shown below:\n\n FS-Cache: Potential volume collision new=00000024 old=00000022\n ......\n INFO: task mount:1148 blocked for more than 122 seconds.\n       Not tainted 6.1.0-rc6+ #1\n task:mount           state:D stack:0     pid:1148  ppid:1\n Call Trace:\n  \u003cTASK\u003e\n  __schedule+0x2f6/0xb80\n  schedule+0x67/0xe0\n  fscache_wait_on_volume_collision.cold+0x80/0x82\n  __fscache_acquire_volume+0x40d/0x4e0\n  erofs_fscache_register_volume+0x51/0xe0 [erofs]\n  erofs_fscache_register_fs+0x19c/0x240 [erofs]\n  erofs_fc_fill_super+0x746/0xaf0 [erofs]\n  vfs_get_super+0x7d/0x100\n  get_tree_nodev+0x16/0x20\n  erofs_fc_get_tree+0x20/0x30 [erofs]\n  vfs_get_tree+0x24/0xb0\n  path_mount+0x2fa/0xa90\n  do_mount+0x7c/0xa0\n  __x64_sys_mount+0x8b/0xe0\n  do_syscall_64+0x30/0x60\n  entry_SYSCALL_64_after_hwframe+0x46/0xb0\n\nConsidering that wake_up_bit() is more selective, so fix it by using\nwait_on_bit() instead of wait_var_event() to wait for the freeing of\nrelinquished volume. In addition because waitqueue_active() is used in\nwake_up_bit() and clear_bit() doesn\u0027t imply any memory barrier, use\nclear_and_wake_up_bit() to add the missing memory barrier between\ncursor-\u003eflags and waitqueue_active()."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T07:46:47.540Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/3be069f42a7b79d3149194f21cdf24bf23864cac"
        },
        {
          "url": "https://git.kernel.org/stable/c/8226e37d82f43657da34dd770e2b38f20242ada7"
        }
      ],
      "title": "fscache: Use wait_on_bit() to wait for the freeing of relinquished volume",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-52982",
    "datePublished": "2025-03-27T16:43:20.735Z",
    "dateReserved": "2025-03-27T16:40:15.740Z",
    "dateUpdated": "2025-05-04T07:46:47.540Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-52982\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-03-27T17:15:45.437\",\"lastModified\":\"2025-03-28T18:11:49.747\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nfscache: Use wait_on_bit() to wait for the freeing of relinquished volume\\n\\nThe freeing of relinquished volume will wake up the pending volume\\nacquisition by using wake_up_bit(), however it is mismatched with\\nwait_var_event() used in fscache_wait_on_volume_collision() and it will\\nnever wake up the waiter in the wait-queue because these two functions\\noperate on different wait-queues.\\n\\nAccording to the implementation in fscache_wait_on_volume_collision(),\\nif the wake-up of pending acquisition is delayed longer than 20 seconds\\n(e.g., due to the delay of on-demand fd closing), the first\\nwait_var_event_timeout() will timeout and the following wait_var_event()\\nwill hang forever as shown below:\\n\\n FS-Cache: Potential volume collision new=00000024 old=00000022\\n ......\\n INFO: task mount:1148 blocked for more than 122 seconds.\\n       Not tainted 6.1.0-rc6+ #1\\n task:mount           state:D stack:0     pid:1148  ppid:1\\n Call Trace:\\n  \u003cTASK\u003e\\n  __schedule+0x2f6/0xb80\\n  schedule+0x67/0xe0\\n  fscache_wait_on_volume_collision.cold+0x80/0x82\\n  __fscache_acquire_volume+0x40d/0x4e0\\n  erofs_fscache_register_volume+0x51/0xe0 [erofs]\\n  erofs_fscache_register_fs+0x19c/0x240 [erofs]\\n  erofs_fc_fill_super+0x746/0xaf0 [erofs]\\n  vfs_get_super+0x7d/0x100\\n  get_tree_nodev+0x16/0x20\\n  erofs_fc_get_tree+0x20/0x30 [erofs]\\n  vfs_get_tree+0x24/0xb0\\n  path_mount+0x2fa/0xa90\\n  do_mount+0x7c/0xa0\\n  __x64_sys_mount+0x8b/0xe0\\n  do_syscall_64+0x30/0x60\\n  entry_SYSCALL_64_after_hwframe+0x46/0xb0\\n\\nConsidering that wake_up_bit() is more selective, so fix it by using\\nwait_on_bit() instead of wait_var_event() to wait for the freeing of\\nrelinquished volume. In addition because waitqueue_active() is used in\\nwake_up_bit() and clear_bit() doesn\u0027t imply any memory barrier, use\\nclear_and_wake_up_bit() to add the missing memory barrier between\\ncursor-\u003eflags and waitqueue_active().\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: fscache: utilice wait_on_bit() para esperar la liberaci\u00f3n del volumen cedido. La liberaci\u00f3n del volumen cedido activar\u00e1 la adquisici\u00f3n de volumen pendiente mediante wake_up_bit(), sin embargo no coincide con wait_var_event() utilizado en fscache_wait_on_volume_collision() y nunca activar\u00e1 al que espera en la cola de espera porque estas dos funciones operan en colas de espera diferentes. Seg\u00fan la implementaci\u00f3n en fscache_wait_on_volume_collision(), si la activaci\u00f3n de una adquisici\u00f3n pendiente se demora m\u00e1s de 20 segundos (por ejemplo, debido a la demora en el cierre del fd a pedido), el primer wait_var_event_timeout() expirar\u00e1 y el siguiente wait_var_event() se colgar\u00e1 para siempre como se muestra a continuaci\u00f3n: FS-Cache: Potencial colisi\u00f3n de volumen nuevo=00000024 antiguo=00000022 ...... INFORMACI\u00d3N: montaje de tarea: 1148 bloqueado durante m\u00e1s de 122 segundos. No contaminado 6.1.0-rc6+ #1 task:mount state:D stack:0 pid:1148 ppid:1 Call Trace:  __schedule+0x2f6/0xb80 schedule+0x67/0xe0 fscache_wait_on_volume_collision.cold+0x80/0x82 __fscache_acquire_volume+0x40d/0x4e0 erofs_fscache_register_volume+0x51/0xe0 [erofs] erofs_fscache_register_fs+0x19c/0x240 [erofs] erofs_fc_fill_super+0x746/0xaf0 [erofs] vfs_get_super+0x7d/0x100 get_tree_nodev+0x16/0x20 erofs_fc_get_tree+0x20/0x30 [erofs] vfs_get_tree+0x24/0xb0 path_mount+0x2fa/0xa90 do_mount+0x7c/0xa0 __x64_sys_mount+0x8b/0xe0 do_syscall_64+0x30/0x60 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Considering that wake_up_bit() es m\u00e1s selectivo, corr\u00edjalo utilizando wait_on_bit() en lugar de wait_var_event() para esperar la liberaci\u00f3n del volumen cedido. Adem\u00e1s, debido a que waitqueue_active() se usa en wake_up_bit() y clear_bit() no implica ninguna barrera de memoria, use clear_and_wake_up_bit() para agregar la barrera de memoria faltante entre cursor-\u0026gt;flags y waitqueue_active().\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/3be069f42a7b79d3149194f21cdf24bf23864cac\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/8226e37d82f43657da34dd770e2b38f20242ada7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


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.