CVE-2023-53531 (GCVE-0-2023-53531)
Vulnerability from cvelistv5
Published
2025-10-01 11:46
Modified
2025-10-01 11:46
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: null_blk: fix poll request timeout handling When doing io_uring benchmark on /dev/nullb0, it's easy to crash the kernel if poll requests timeout triggered, as reported by David. [1] BUG: kernel NULL pointer dereference, address: 0000000000000008 Workqueue: kblockd blk_mq_timeout_work RIP: 0010:null_timeout_rq+0x4e/0x91 Call Trace: ? null_timeout_rq+0x4e/0x91 blk_mq_handle_expired+0x31/0x4b bt_iter+0x68/0x84 ? bt_tags_iter+0x81/0x81 __sbitmap_for_each_set.constprop.0+0xb0/0xf2 ? __blk_mq_complete_request_remote+0xf/0xf bt_for_each+0x46/0x64 ? __blk_mq_complete_request_remote+0xf/0xf ? percpu_ref_get_many+0xc/0x2a blk_mq_queue_tag_busy_iter+0x14d/0x18e blk_mq_timeout_work+0x95/0x127 process_one_work+0x185/0x263 worker_thread+0x1b5/0x227 This is indeed a race problem between null_timeout_rq() and null_poll(). null_poll() null_timeout_rq() spin_lock(&nq->poll_lock) list_splice_init(&nq->poll_list, &list) spin_unlock(&nq->poll_lock) while (!list_empty(&list)) req = list_first_entry() list_del_init() ... blk_mq_add_to_batch() // req->rq_next = NULL spin_lock(&nq->poll_lock) // rq->queuelist->next == NULL list_del_init(&rq->queuelist) spin_unlock(&nq->poll_lock) Fix these problems by setting requests state to MQ_RQ_COMPLETE under nq->poll_lock protection, in which null_timeout_rq() can safely detect this race and early return. Note this patch just fix the kernel panic when request timeout happen. [1] https://lore.kernel.org/all/3893581.1691785261@warthog.procyon.org.uk/
Impacted products
Vendor Product Version
Linux Linux Version: 0a593fbbc245a85940ed34caa3aa1e4cb060c54b
Version: 0a593fbbc245a85940ed34caa3aa1e4cb060c54b
Version: 0a593fbbc245a85940ed34caa3aa1e4cb060c54b
Create a notification for this product.
   Linux Linux Version: 5.16
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/block/null_blk/main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a0b4a0666beacfe8add9c71d8922475541dbae73",
              "status": "affected",
              "version": "0a593fbbc245a85940ed34caa3aa1e4cb060c54b",
              "versionType": "git"
            },
            {
              "lessThan": "a7cb2e709f2927cc3c76781df3e45de2381b3b9d",
              "status": "affected",
              "version": "0a593fbbc245a85940ed34caa3aa1e4cb060c54b",
              "versionType": "git"
            },
            {
              "lessThan": "5a26e45edb4690d58406178b5a9ea4c6dcf2c105",
              "status": "affected",
              "version": "0a593fbbc245a85940ed34caa3aa1e4cb060c54b",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/block/null_blk/main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.16"
            },
            {
              "lessThan": "5.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.54",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.5.*",
              "status": "unaffected",
              "version": "6.5.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.6",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.54",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.5.4",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6",
                  "versionStartIncluding": "5.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix poll request timeout handling\n\nWhen doing io_uring benchmark on /dev/nullb0, it\u0027s easy to crash the\nkernel if poll requests timeout triggered, as reported by David. [1]\n\nBUG: kernel NULL pointer dereference, address: 0000000000000008\nWorkqueue: kblockd blk_mq_timeout_work\nRIP: 0010:null_timeout_rq+0x4e/0x91\nCall Trace:\n ? null_timeout_rq+0x4e/0x91\n blk_mq_handle_expired+0x31/0x4b\n bt_iter+0x68/0x84\n ? bt_tags_iter+0x81/0x81\n __sbitmap_for_each_set.constprop.0+0xb0/0xf2\n ? __blk_mq_complete_request_remote+0xf/0xf\n bt_for_each+0x46/0x64\n ? __blk_mq_complete_request_remote+0xf/0xf\n ? percpu_ref_get_many+0xc/0x2a\n blk_mq_queue_tag_busy_iter+0x14d/0x18e\n blk_mq_timeout_work+0x95/0x127\n process_one_work+0x185/0x263\n worker_thread+0x1b5/0x227\n\nThis is indeed a race problem between null_timeout_rq() and null_poll().\n\nnull_poll()\t\t\t\tnull_timeout_rq()\n  spin_lock(\u0026nq-\u003epoll_lock)\n  list_splice_init(\u0026nq-\u003epoll_list, \u0026list)\n  spin_unlock(\u0026nq-\u003epoll_lock)\n\n  while (!list_empty(\u0026list))\n    req = list_first_entry()\n    list_del_init()\n    ...\n    blk_mq_add_to_batch()\n    // req-\u003erq_next = NULL\n\t\t\t\t\tspin_lock(\u0026nq-\u003epoll_lock)\n\n\t\t\t\t\t// rq-\u003equeuelist-\u003enext == NULL\n\t\t\t\t\tlist_del_init(\u0026rq-\u003equeuelist)\n\n\t\t\t\t\tspin_unlock(\u0026nq-\u003epoll_lock)\n\nFix these problems by setting requests state to MQ_RQ_COMPLETE under\nnq-\u003epoll_lock protection, in which null_timeout_rq() can safely detect\nthis race and early return.\n\nNote this patch just fix the kernel panic when request timeout happen.\n\n[1] https://lore.kernel.org/all/3893581.1691785261@warthog.procyon.org.uk/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-10-01T11:46:15.949Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a0b4a0666beacfe8add9c71d8922475541dbae73"
        },
        {
          "url": "https://git.kernel.org/stable/c/a7cb2e709f2927cc3c76781df3e45de2381b3b9d"
        },
        {
          "url": "https://git.kernel.org/stable/c/5a26e45edb4690d58406178b5a9ea4c6dcf2c105"
        }
      ],
      "title": "null_blk: fix poll request timeout handling",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53531",
    "datePublished": "2025-10-01T11:46:15.949Z",
    "dateReserved": "2025-10-01T11:39:39.408Z",
    "dateUpdated": "2025-10-01T11:46:15.949Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-53531\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-10-01T12:15:57.843\",\"lastModified\":\"2025-10-02T19:11:46.753\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnull_blk: fix poll request timeout handling\\n\\nWhen doing io_uring benchmark on /dev/nullb0, it\u0027s easy to crash the\\nkernel if poll requests timeout triggered, as reported by David. [1]\\n\\nBUG: kernel NULL pointer dereference, address: 0000000000000008\\nWorkqueue: kblockd blk_mq_timeout_work\\nRIP: 0010:null_timeout_rq+0x4e/0x91\\nCall Trace:\\n ? null_timeout_rq+0x4e/0x91\\n blk_mq_handle_expired+0x31/0x4b\\n bt_iter+0x68/0x84\\n ? bt_tags_iter+0x81/0x81\\n __sbitmap_for_each_set.constprop.0+0xb0/0xf2\\n ? __blk_mq_complete_request_remote+0xf/0xf\\n bt_for_each+0x46/0x64\\n ? __blk_mq_complete_request_remote+0xf/0xf\\n ? percpu_ref_get_many+0xc/0x2a\\n blk_mq_queue_tag_busy_iter+0x14d/0x18e\\n blk_mq_timeout_work+0x95/0x127\\n process_one_work+0x185/0x263\\n worker_thread+0x1b5/0x227\\n\\nThis is indeed a race problem between null_timeout_rq() and null_poll().\\n\\nnull_poll()\\t\\t\\t\\tnull_timeout_rq()\\n  spin_lock(\u0026nq-\u003epoll_lock)\\n  list_splice_init(\u0026nq-\u003epoll_list, \u0026list)\\n  spin_unlock(\u0026nq-\u003epoll_lock)\\n\\n  while (!list_empty(\u0026list))\\n    req = list_first_entry()\\n    list_del_init()\\n    ...\\n    blk_mq_add_to_batch()\\n    // req-\u003erq_next = NULL\\n\\t\\t\\t\\t\\tspin_lock(\u0026nq-\u003epoll_lock)\\n\\n\\t\\t\\t\\t\\t// rq-\u003equeuelist-\u003enext == NULL\\n\\t\\t\\t\\t\\tlist_del_init(\u0026rq-\u003equeuelist)\\n\\n\\t\\t\\t\\t\\tspin_unlock(\u0026nq-\u003epoll_lock)\\n\\nFix these problems by setting requests state to MQ_RQ_COMPLETE under\\nnq-\u003epoll_lock protection, in which null_timeout_rq() can safely detect\\nthis race and early return.\\n\\nNote this patch just fix the kernel panic when request timeout happen.\\n\\n[1] https://lore.kernel.org/all/3893581.1691785261@warthog.procyon.org.uk/\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/5a26e45edb4690d58406178b5a9ea4c6dcf2c105\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a0b4a0666beacfe8add9c71d8922475541dbae73\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a7cb2e709f2927cc3c76781df3e45de2381b3b9d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…