CVE-2023-53810: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-jxhv-6vcg-8ffm
Share
CVSS 7.8
Published
Advisory Summary

CVE-2023-53810 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2023-53810 at a Glance

CVE Identifier CVE-2023-53810
GHSA Identifier GHSA-jxhv-6vcg-8ffm
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2023-53810

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2023-53810, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2023-53810 NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-53810
git.kernel.org/stable/c/7d206ec7a0... WEB
https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f
git.kernel.org/stable/c/874bdf43b4... WEB
https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08
git.kernel.org/stable/c/92d5d233b9... WEB
https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633
git.kernel.org/stable/c/9cd1e56667... WEB
https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603
git.kernel.org/stable/c/b278570e2c... WEB
https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4
git.kernel.org/stable/c/d206f79d9c... WEB
https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c

Frequently Asked Questions

What is CVE-2023-53810?
CVE-2023-53810 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2023-53810?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2023-53810?
CVE-2023-53810 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2023-53810?
CVE-2023-53810 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2023-53810?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jxhv-6vcg-8ffm",
  "modified" : "2026-08-04T12:34:39Z",
  "published" : "2025-12-09T03:31:11Z",
  "aliases" : [ "CVE-2023-53810" ],
  "details" : "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't 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 'slot_refs != 0' without there being an actual bug.\n\nThis makes __blk_crypto_evict_key() hit the\n'WARN_ON_ONCE(atomic_read(&slot->slot_refs) != 0)' 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's last bio, or make\n__blk_crypto_evict_key() ignore slot_refs.  Let's 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-53810"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d206ec7a04e8545828191b6ea8b49d3ea61391f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/874bdf43b4a7dc5463c31508f62b3e42eb237b08"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/92d5d233b9ff531cf9cc36ab4251779e07adb633"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9cd1e566676bbcb8a126acd921e4e194e6339603"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b278570e2c59d538216f8b656e97680188a8fba4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d206f79d9cd658665b37ce8134c6ec849ac7af0c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-12-09T01:16:53Z"
  }
}