Menu

Star on GitHub · 3.5k

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 quies…

Published Sep 17, 2026EPSS 0.20%

Overview

CVE-2026-93057 is a known-severity vulnerability. It was published on September 17, 2026.

Technical 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]

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.

Frequently asked questions

What is CVE-2026-93057?

CVE-2026-93057 is a known-severity vulnerability. It was published on September 17, 2026.

How severe is CVE-2026-93057?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-93057?

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.

How can CyberStrike help with CVE-2026-93057?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-93057 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach