GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2023-53810 (GCVE-0-2023-53810)

Vulnerability from cvelistv5 – Published: 2025-12-09 00:01 – Updated: 2026-08-05 09:16
VLAI
Title
blk-mq: release crypto keyslot before reporting I/O complete
Summary
In the Linux kernel, the following vulnerability has been resolved: blk-mq: release crypto keyslot before reporting I/O complete Once all I/O using a blk_crypto_key has completed, filesystems can call blk_crypto_evict_key(). However, the block layer currently doesn't call blk_crypto_put_keyslot() until the request is being freed, which happens after upper layers have been told (via bio_endio()) the I/O has completed. This causes a race condition where blk_crypto_evict_key() can see 'slot_refs != 0' without there being an actual bug. This makes __blk_crypto_evict_key() hit the 'WARN_ON_ONCE(atomic_read(&slot->slot_refs) != 0)' and return without doing anything, eventually causing a use-after-free in blk_crypto_reprogram_all_keys(). (This is a very rare bug and has only been seen when per-file keys are being used with fscrypt.) There are two options to fix this: either release the keyslot before bio_endio() is called on the request's last bio, or make __blk_crypto_evict_key() ignore slot_refs. Let's go with the first solution, since it preserves the ability to report bugs (via WARN_ON_ONCE) where a key is evicted while still in-use.
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 874bdf43b4a7dc5463c31508f62b3e42eb237b08 (git)
Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < d206f79d9cd658665b37ce8134c6ec849ac7af0c (git)
Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 7d206ec7a04e8545828191b6ea8b49d3ea61391f (git)
Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < b278570e2c59d538216f8b656e97680188a8fba4 (git)
Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 92d5d233b9ff531cf9cc36ab4251779e07adb633 (git)
Affected: a892c8d52c02284076fbbacae6692aa5c5807d11 , < 9cd1e566676bbcb8a126acd921e4e194e6339603 (git)
guessed Create a notification for this product.
Linux Linux Affected: 5.8
Unaffected: 0 , < 5.8 (semver)
Unaffected: 5.10.180 , ≤ 5.10.* (semver)
Unaffected: 5.15.111 , ≤ 5.15.* (semver)
Unaffected: 6.1.28 , ≤ 6.1.* (semver)
Unaffected: 6.2.15 , ≤ 6.2.* (semver)
Unaffected: 6.3.2 , ≤ 6.3.* (semver)
Unaffected: 6.4 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "block/blk-crypto-internal.h",
            "block/blk-crypto.c",
            "block/blk-merge.c",
            "block/blk-mq.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "874bdf43b4a7dc5463c31508f62b3e42eb237b08",
              "status": "affected",
              "version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
              "versionType": "git"
            },
            {
              "lessThan": "d206f79d9cd658665b37ce8134c6ec849ac7af0c",
              "status": "affected",
              "version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
              "versionType": "git"
            },
            {
              "lessThan": "7d206ec7a04e8545828191b6ea8b49d3ea61391f",
              "status": "affected",
              "version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
              "versionType": "git"
            },
            {
              "lessThan": "b278570e2c59d538216f8b656e97680188a8fba4",
              "status": "affected",
              "version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
              "versionType": "git"
            },
            {
              "lessThan": "92d5d233b9ff531cf9cc36ab4251779e07adb633",
              "status": "affected",
              "version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
              "versionType": "git"
            },
            {
              "lessThan": "9cd1e566676bbcb8a126acd921e4e194e6339603",
              "status": "affected",
              "version": "a892c8d52c02284076fbbacae6692aa5c5807d11",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "block/blk-crypto-internal.h",
            "block/blk-crypto.c",
            "block/blk-merge.c",
            "block/blk-mq.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.8"
            },
            {
              "lessThan": "5.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.180",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.111",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.28",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.2.*",
              "status": "unaffected",
              "version": "6.2.15",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.3.*",
              "status": "unaffected",
              "version": "6.3.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.4",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.180",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.111",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.28",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2.15",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.3.2",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.4",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblk-mq: release crypto keyslot before reporting I/O complete\n\nOnce all I/O using a blk_crypto_key has completed, filesystems can call\nblk_crypto_evict_key().  However, the block layer currently doesn\u0027t call\nblk_crypto_put_keyslot() until the request is being freed, which happens\nafter upper layers have been told (via bio_endio()) the I/O has\ncompleted.  This causes a race condition where blk_crypto_evict_key()\ncan see \u0027slot_refs != 0\u0027 without there being an actual bug.\n\nThis makes __blk_crypto_evict_key() hit the\n\u0027WARN_ON_ONCE(atomic_read(\u0026slot-\u003eslot_refs) != 0)\u0027 and return without\ndoing anything, eventually causing a use-after-free in\nblk_crypto_reprogram_all_keys().  (This is a very rare bug and has only\nbeen seen when per-file keys are being used with fscrypt.)\n\nThere are two options to fix this: either release the keyslot before\nbio_endio() is called on the request\u0027s last bio, or make\n__blk_crypto_evict_key() ignore slot_refs.  Let\u0027s go with the first\nsolution, since it preserves the ability to report bugs (via\nWARN_ON_ONCE) where a key is evicted while still in-use."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Triggering requires local filesystem I/O on an fscrypt-encrypted file plus locally-driven inode/key eviction (unlink/close or FS_IOC_REMOVE_ENCRYPTION_KEY), all via ordinary syscalls on the local system. No network protocol handler is involved.\nAC:L - The attacker controls both sides of the race \u2014 submitting encrypted I/O and forcing key eviction \u2014 and can retry the loop indefinitely across threads/CPUs until the window between bio_endio() and blk_mq_free_request() is hit. The subsequent reprogram_all_keys() trigger occurs routinely on suspend/resume and UFS error recovery, so no attacker-uncontrollable precondition gates exploitation.\nPR:L - Only an ordinary unprivileged local account (or an Android app) with write access to an fscrypt-encrypted directory is needed; per-file keys are the default fscrypt mode and every app\u0027s data directory qualifies. No capabilities or root are required.\nUI:N - The attacker performs every step \u2014 the I/O, the key eviction, and the heap spray \u2014 with no action from any other user. Device reset/resume that consumes the dangling pointer happens automatically or can be induced by the attacker.\nS:U - The use-after-free and the resulting memory corruption occur within the kernel\u0027s own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The freed blk_crypto_key is re-read and its attacker-controlled crypto_mode is used as an unbounded array index in ufshcd_crypto_keyslot_program(), yielding an arbitrary out-of-bounds kernel read oracle; the stale keyslot also causes stored data to be decrypted under the wrong key, compromising fscrypt\u0027s confidentiality guarantees.\nI:H - The same UAF gives an attacker-controlled key-\u003esize to a memcpy into a 72-byte stack union, an unbounded stack buffer overflow with attacker-supplied bytes suitable for control-flow hijacking; additionally, attacker-chosen key material can be programmed into hardware keyslots and on-disk data silently encrypted under the wrong key.\nA:H - The immediate effect is a WARN_ON_ONCE (a panic under panic_on_warn) and a use-after-free that dereferences freed/wild pointers during UFS reset or resume, causing kernel oops or panic; corrupting the hardware keyslot state also breaks storage encryption and can render the filesystem unusable."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T09:16:09.388Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08"
        },
        {
          "url": "https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c"
        },
        {
          "url": "https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f"
        },
        {
          "url": "https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4"
        },
        {
          "url": "https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633"
        },
        {
          "url": "https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603"
        }
      ],
      "title": "blk-mq: release crypto keyslot before reporting I/O complete",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53810",
    "datePublished": "2025-12-09T00:01:08.062Z",
    "dateReserved": "2025-12-08T23:58:35.276Z",
    "dateUpdated": "2026-08-05T09:16:09.388Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2023-53810",
      "date": "2026-09-14",
      "epss": "0.00142",
      "percentile": "0.03839"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-53810\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-09T01:16:53.073\",\"lastModified\":\"2026-08-04T10:19:22.320\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nblk-mq: release crypto keyslot before reporting I/O complete\\n\\nOnce all I/O using a blk_crypto_key has completed, filesystems can call\\nblk_crypto_evict_key().  However, the block layer currently doesn\u0027t call\\nblk_crypto_put_keyslot() until the request is being freed, which happens\\nafter upper layers have been told (via bio_endio()) the I/O has\\ncompleted.  This causes a race condition where blk_crypto_evict_key()\\ncan see \u0027slot_refs != 0\u0027 without there being an actual bug.\\n\\nThis makes __blk_crypto_evict_key() hit the\\n\u0027WARN_ON_ONCE(atomic_read(\u0026slot-\u003eslot_refs) != 0)\u0027 and return without\\ndoing anything, eventually causing a use-after-free in\\nblk_crypto_reprogram_all_keys().  (This is a very rare bug and has only\\nbeen seen when per-file keys are being used with fscrypt.)\\n\\nThere are two options to fix this: either release the keyslot before\\nbio_endio() is called on the request\u0027s last bio, or make\\n__blk_crypto_evict_key() ignore slot_refs.  Let\u0027s go with the first\\nsolution, since it preserves the ability to report bugs (via\\nWARN_ON_ONCE) where a key is evicted while still in-use.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"block/blk-crypto-internal.h\",\"block/blk-crypto.c\",\"block/blk-merge.c\",\"block/blk-mq.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"a892c8d52c02284076fbbacae6692aa5c5807d11\",\"lessThan\":\"874bdf43b4a7dc5463c31508f62b3e42eb237b08\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"a892c8d52c02284076fbbacae6692aa5c5807d11\",\"lessThan\":\"d206f79d9cd658665b37ce8134c6ec849ac7af0c\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"a892c8d52c02284076fbbacae6692aa5c5807d11\",\"lessThan\":\"7d206ec7a04e8545828191b6ea8b49d3ea61391f\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"a892c8d52c02284076fbbacae6692aa5c5807d11\",\"lessThan\":\"b278570e2c59d538216f8b656e97680188a8fba4\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"a892c8d52c02284076fbbacae6692aa5c5807d11\",\"lessThan\":\"92d5d233b9ff531cf9cc36ab4251779e07adb633\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"a892c8d52c02284076fbbacae6692aa5c5807d11\",\"lessThan\":\"9cd1e566676bbcb8a126acd921e4e194e6339603\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"block/blk-crypto-internal.h\",\"block/blk-crypto.c\",\"block/blk-merge.c\",\"block/blk-mq.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.8\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.8\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.10.180\",\"lessThanOrEqual\":\"5.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.111\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.28\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.2.15\",\"lessThanOrEqual\":\"6.2.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.3.2\",\"lessThanOrEqual\":\"6.3.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.4\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-04T19:15:33+00:00",
      "cve": "CVE-2023-53810",
      "id": "CVE-2023-53810",
      "initial_release_date": "2023-01-01T00:00:00+00:00",
      "product_status:fixed": "279",
      "product_status:known_affected": "22",
      "product_status:known_not_affected": "166",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: blk-mq: release crypto keyslot before reporting I/O complete",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2023/cve-2023-53810.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.