CVE-2023-53760: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6mjv-x284-3fg6
Published
Advisory Summary

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

CVE-2023-53760 at a Glance

CVE Identifier CVE-2023-53760
GHSA Identifier GHSA-6mjv-x284-3fg6
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2023-53760

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-53760, 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: scsi: ufs: core: mcq: Fix &hwq->cq_lock deadlock issue When ufshcd_err_handler() is executed, CQ event interrupt can enter waiting for the same lock. This can happen in ufshcd_handle_mcq_cq_events() and also in ufs_mtk_mcq_intr(). The following warning message will be generated when &hwq->cq_lock is used in IRQ context with IRQ enabled. Use ufshcd_mcq_poll_cqe_lock() with spin_lock_irqsave instead of spin_lock to resolve the deadlock issue. [name:lockdep&]WARNING: inconsistent lock state [name:lockdep&]-------------------------------- [name:lockdep&]inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage. [name:lockdep&]kworker/u16:4/260 [HC0[0]:SC0[0]:HE1:SE1] takes: ffffff8028444600 (&hwq->cq_lock){?.-.}-{2:2}, at: ufshcd_mcq_poll_cqe_lock+0x30/0xe0 [name:lockdep&]{IN-HARDIRQ-W} state was registered at: lock_acquire+0x17c/0x33c _raw_spin_lock+0x5c/0x7c ufshcd_mcq_poll_cqe_lock+0x30/0xe0 ufs_mtk_mcq_intr+0x60/0x1bc [ufs_mediatek_mod] __handle_irq_event_percpu+0x140/0x3ec handle_irq_event+0x50/0xd8 handle_fasteoi_irq+0x148/0x2b0 generic_handle_domain_irq+0x4c/0x6c gic_handle_irq+0x58/0x134 call_on_irq_stack+0x40/0x74 do_interrupt_handler+0x84/0xe4 el1_interrupt+0x3c/0x78 <snip> Possible unsafe locking scenario: CPU0 ---- lock(&hwq->cq_lock); <Interrupt> lock(&hwq->cq_lock); *** DEADLOCK *** 2 locks held by kworker/u16:4/260: [name:lockdep&] stack backtrace: CPU: 7 PID: 260 Comm: kworker/u16:4 Tainted: G S W OE 6.1.17-mainline-android14-2-g277223301adb #1 Workqueue: ufs_eh_wq_0 ufshcd_err_handler Call trace: dump_backtrace+0x10c/0x160 show_stack+0x20/0x30 dump_stack_lvl+0x98/0xd8 dump_stack+0x20/0x60 print_usage_bug+0x584/0x76c mark_lock_irq+0x488/0x510 mark_lock+0x1ec/0x25c __lock_acquire+0x4d8/0xffc lock_acquire+0x17c/0x33c _raw_spin_lock+0x5c/0x7c ufshcd_mcq_poll_cqe_lock+0x30/0xe0 ufshcd_poll+0x68/0x1b0 ufshcd_transfer_req_compl+0x9c/0xc8 ufshcd_err_handler+0x3bc/0xea0 process_one_work+0x2f4/0x7e8 worker_thread+0x234/0x450 kthread+0x110/0x134 ret_from_fork+0x10/0x20

References

Frequently Asked Questions

What is CVE-2023-53760?
CVE-2023-53760 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-53760?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2023-53760?
CVE-2023-53760 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2023-53760?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6mjv-x284-3fg6",
  "modified" : "2025-12-08T03:31:03Z",
  "published" : "2025-12-08T03:31:03Z",
  "aliases" : [ "CVE-2023-53760" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: mcq: Fix &hwq->cq_lock deadlock issue\n\nWhen ufshcd_err_handler() is executed, CQ event interrupt can enter waiting\nfor the same lock. This can happen in ufshcd_handle_mcq_cq_events() and\nalso in ufs_mtk_mcq_intr(). The following warning message will be generated\nwhen &hwq->cq_lock is used in IRQ context with IRQ enabled. Use\nufshcd_mcq_poll_cqe_lock() with spin_lock_irqsave instead of spin_lock to\nresolve the deadlock issue.\n\n[name:lockdep&]WARNING: inconsistent lock state\n[name:lockdep&]--------------------------------\n[name:lockdep&]inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.\n[name:lockdep&]kworker/u16:4/260 [HC0[0]:SC0[0]:HE1:SE1] takes:\n  ffffff8028444600 (&hwq->cq_lock){?.-.}-{2:2}, at:\nufshcd_mcq_poll_cqe_lock+0x30/0xe0\n[name:lockdep&]{IN-HARDIRQ-W} state was registered at:\n  lock_acquire+0x17c/0x33c\n  _raw_spin_lock+0x5c/0x7c\n  ufshcd_mcq_poll_cqe_lock+0x30/0xe0\n  ufs_mtk_mcq_intr+0x60/0x1bc [ufs_mediatek_mod]\n  __handle_irq_event_percpu+0x140/0x3ec\n  handle_irq_event+0x50/0xd8\n  handle_fasteoi_irq+0x148/0x2b0\n  generic_handle_domain_irq+0x4c/0x6c\n  gic_handle_irq+0x58/0x134\n  call_on_irq_stack+0x40/0x74\n  do_interrupt_handler+0x84/0xe4\n  el1_interrupt+0x3c/0x78\n<snip>\n\nPossible unsafe locking scenario:\n       CPU0\n       ----\n  lock(&hwq->cq_lock);\n  <Interrupt>\n    lock(&hwq->cq_lock);\n  *** DEADLOCK ***\n2 locks held by kworker/u16:4/260:\n\n[name:lockdep&]\n stack backtrace:\nCPU: 7 PID: 260 Comm: kworker/u16:4 Tainted: G S      W  OE\n6.1.17-mainline-android14-2-g277223301adb #1\nWorkqueue: ufs_eh_wq_0 ufshcd_err_handler\n\n Call trace:\n  dump_backtrace+0x10c/0x160\n  show_stack+0x20/0x30\n  dump_stack_lvl+0x98/0xd8\n  dump_stack+0x20/0x60\n  print_usage_bug+0x584/0x76c\n  mark_lock_irq+0x488/0x510\n  mark_lock+0x1ec/0x25c\n  __lock_acquire+0x4d8/0xffc\n  lock_acquire+0x17c/0x33c\n  _raw_spin_lock+0x5c/0x7c\n  ufshcd_mcq_poll_cqe_lock+0x30/0xe0\n  ufshcd_poll+0x68/0x1b0\n  ufshcd_transfer_req_compl+0x9c/0xc8\n  ufshcd_err_handler+0x3bc/0xea0\n  process_one_work+0x2f4/0x7e8\n  worker_thread+0x234/0x450\n  kthread+0x110/0x134\n  ret_from_fork+0x10/0x20",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-53760"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2ce8c49c7b53e0a2258b833eeab16a6d78f732d1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/948afc69615167a3c82430f99bfd046332b89912"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-12-08T02:15:51Z"
  }
}