CVE-2026-93057
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Avoid possible memory reclaim deadlock in TX EQTR context TX EQTR may run while devfreq gear scaling has quiesced the UFS tagset. In that context, functions ufshcd_tx_eqtr(), __ufshcd_tx_eqtr() and ufs_qcom_get_rx_fom() allocate memory with GFP_KERNEL. If direct reclaim is triggered, reclaim/writeback can depend on I/O to UFS device. Because the queue is quiesced, this can cause deadlock. Use memalloc_noio_save/restore() in ufshcd_tx_eqtr() to cover all allocations in the TX EQTR call tree, including: - params->eqtr_record in ufshcd_tx_eqtr() - eqtr_data in __ufshcd_tx_eqtr() - params in ufs_qcom_get_rx_fom() This is preferred over tagging individual call sites with GFP_NOIO, as it automatically covers any future allocations added anywhere in the call tree without requiring each caller to be aware of this constraint. [mkp: fix label as suggested by Bart]
Affected versions
Linux kernel versions
7.1
and later are affected. Fixed in
7.2.6,
7.3-rc1
and their respective stable series.
References
2 totalFrequently asked questions
-
What is CVE-2026-93057?
CVE-2026-93057 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 7.1 onward and has been patched in 7.2.6 and 7.3-rc1. CVE-2026-93057 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-93057?
Yes. CVE-2026-93057 has been patched. Fixed versions include 7.2.6 and 7.3-rc1. If you are running Linux kernel 7.1 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-93057 actively exploited?
No. CVE-2026-93057 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.