VulnerabilityPublished 17 Sep 2026Updated 19 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to a28a7d9b3bb116da788ae492c90465ec1a7fa6e8 or 760fc6f0e25a72832c2fcf37ecf5f1b770ec8374 when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in a28a7d9b3bb116da788ae492c90465ec1a7fa6e8, 760fc6f0e25a72832c2fcf37ecf5f1b770ec8374

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to a28a7d9b3bb116da788ae492c90465ec1a7fa6e8 or 760fc6f0e25a72832c2fcf37ecf5f1b770ec8374.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 03e5d38e2f985d8d0b0a60508c0b422f664808e3, < a28a7d9b3bb116da788ae492c90465ec1a7fa6e8	Fixed in a28a7d9b3bb116da788ae492c90465ec1a7fa6e8
LinuxLinux	Affected ≥ 03e5d38e2f985d8d0b0a60508c0b422f664808e3, < 760fc6f0e25a72832c2fcf37ecf5f1b770ec8374	Fixed in 760fc6f0e25a72832c2fcf37ecf5f1b770ec8374
LinuxLinux	Affected =7.1	Fixed in–

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]

References

Community reviews

Loading reviews…