CVE-2023-53760

/// Technical description

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

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References