Vulnerability · CVE-2023-53760
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
Published Dec 8, 2025 · catalog updated May 11, 2026 · Linux Linux
Last checked Oct 26, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2023-53760. EPSS is 0.17%. Act only if a listed version of Linux Linux is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-99164 · Unknown
- CVE-2026-99100 · Unknown
- CVE-2026-99191 · Medium
- CVE-2026-99192 · High
- CVE-2026-99195 · Medium
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.17%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux ed975065c31c2a0372e13c19e8140b69814a98ba <948afc69615167a3c82430f99bfd046332b89912
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&]------------------------
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux ed975065c31c2a0372e13c19e8140b69814a98ba <948afc69615167a3c82430f99bfd046332b89912ed975065c31c2a0372e13c19e8140b69814a98ba <948afc69615167a3c82430f99bfd046332b89912
How to fix CVE-2023-53760
Upgrade
CVE-2023-53760 lists a fix boundary at 948afc69615167a3c82430f99bfd046332b89912. Compare the installed build with that boundary before you change production.
Version check
Seen in ed975065c31c2a0372e13c19e8140b69814a98ba <948afc69615167a3c82430f99bfd046332b89912
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2023-53760. EPSS is 0.17%. Act only if a listed version of Linux Linux is installed.
Which versions are affected?
Compare what you have installed with Linux Linux ed975065c31c2a0372e13c19e8140b69814a98ba <948afc69615167a3c82430f99bfd046332b89912 ed975065c31c2a0372e13c19e8140b69814a98ba <948afc69615167a3c82430f99bfd046332b89912. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.17%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Dec 8, 2025 · EUVD
Detected
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 en
May 11, 2026 · EUVD
Updated
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 en
Sources
- CVE.orgVulnerability recordCVE-2023-53760
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2023-53760
30-day exploitation probability 0.17%
first.org - EUVDVulnerability recordEUVD-2023-60068
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 u
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 26, 2026
- CVE.orgOct 26, 2026
- EUVDOct 26, 2026