CVE-2026-93057

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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]

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

References (2)

Vendor Advisories for CVE-2026-93057(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-02 12:42 UTCGHSA enrichment
  2. 2026-10-01 19:51 UTCEPSS rescore
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-29 13:45 UTCEG score recompute
  5. 2026-09-29 13:45 UTCGHSA enrichment
  6. 2026-09-28 13:52 UTCEPSS rescore
  7. 2026-09-28 13:52 UTCEPSS rescore
  8. 2026-09-27 13:49 UTCEPSS rescore
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 14:37 UTCGHSA enrichment
  11. 2026-09-24 14:04 UTCEPSS rescore
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-23 15:35 UTCGHSA enrichment
  14. 2026-09-22 16:01 UTCEPSS rescore
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-20 16:38 UTCEG score recompute
  18. 2026-09-20 16:38 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 17:24 UTCNVD update
  21. 2026-09-17 16:22 UTCEG score recompute
  22. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-93057?
CVE-2026-93057 is a publicly disclosed vulnerability published on September 17, 2026. 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 ufshcdtxeqtr(), ufshcdtxeqtr() and ufsqcomgetrxfom()…
When was CVE-2026-93057 disclosed?
CVE-2026-93057 was first published on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93057 actively exploited?
CVE-2026-93057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-93057?
No fix for CVE-2026-93057 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93057 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93057

Explore →

Is Your Infrastructure Affected by CVE-2026-93057?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs