{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53760 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53760 is a denial of service vulnerability in Linux, published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-53760 and fix it if it is affected.\n\nWhat it is: CVE-2023-53760 is a denial of service vulnerability in Linux, published on 8 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-53760 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-53760/ (Markdown: https://insights.sbomify.com/CVE-2023-53760/index.md)","id":"CVE-2023-53760","markdown":"https://insights.sbomify.com/CVE-2023-53760/index.md","name":"CVE-2023-53760","record":{"aliases":["BELL-CVE-2023-53760","GHSA-6mjv-x284-3fg6","UBUNTU-CVE-2023-53760"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A deadlock in the Linux kernel UFS driver can cause a system hang when error handling and interrupts contend for the same lock.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: mcq: Fix \u0026hwq-\u003ecq_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 \u0026hwq-\u003ecq_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\u0026]WARNING: inconsistent lock state\n[name:lockdep\u0026]--------------------------------\n[name:lockdep\u0026]inconsistent {IN-HARDIRQ-W} -\u003e {HARDIRQ-ON-W} usage.\n[name:lockdep\u0026]kworker/u16:4/260 [HC0[0]:SC0[0]:HE1:SE1] takes:\n  ffffff8028444600 (\u0026hwq-\u003ecq_lock){?.-.}-{2:2}, at:\nufshcd_mcq_poll_cqe_lock+0x30/0xe0\n[name:lockdep\u0026]{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\u003csnip\u003e\n\nPossible unsafe locking scenario:\n       CPU0\n       ----\n  lock(\u0026hwq-\u003ecq_lock);\n  \u003cInterrupt\u003e\n    lock(\u0026hwq-\u003ecq_lock);\n  *** DEADLOCK ***\n2 locks held by kworker/u16:4/260:\n\n[name:lockdep\u0026]\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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"scsi: ufs: core: mcq: Fix \u0026hwq-\u003ecq_lock deadlock issue","id":"CVE-2023-53760","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"USB: usbtmc: Fix direction for 0-length ioctl control messages","id":"CVE-2023-53761"},"packages":[],"prev":{"headline":"HID: hidraw: fix data race on device refcount","id":"CVE-2023-53759"},"products":["Linux"],"published":"2025-12-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A deadlock in the Linux kernel UFS driver can cause a system hang when error handling and interrupts contend for the same lock.","url":"https://insights.sbomify.com/CVE-2023-53760/"}