CVE-2026-93057: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-2rmf-84jj-472q
Share
Published
Advisory Summary

CVE-2026-93057 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-93057 at a Glance

CVE Identifier CVE-2026-93057
GHSA Identifier GHSA-2rmf-84jj-472q
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-93057

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-93057, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

NVD — CVE-2026-93057 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93057
git.kernel.org/stable/c/760fc6f0e2... WEB
https://git.kernel.org/stable/c/760fc6f0e25a72832c2fcf37ecf5f1b770ec8374
git.kernel.org/stable/c/a28a7d9b3b... WEB
https://git.kernel.org/stable/c/a28a7d9b3bb116da788ae492c90465ec1a7fa6e8

Frequently Asked Questions

What is CVE-2026-93057?
CVE-2026-93057 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-93057?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93057?
CVE-2026-93057 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93057?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2rmf-84jj-472q",
  "modified" : "2026-09-17T18:32:08Z",
  "published" : "2026-09-17T18:32:08Z",
  "aliases" : [ "CVE-2026-93057" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: Avoid possible memory reclaim deadlock in TX EQTR context\n\nTX EQTR may run while devfreq gear scaling has quiesced the UFS\ntagset. In that context, functions ufshcd_tx_eqtr(), __ufshcd_tx_eqtr()\nand ufs_qcom_get_rx_fom() allocate memory with GFP_KERNEL. If direct\nreclaim is triggered, reclaim/writeback can depend on I/O to UFS\ndevice. Because the queue is quiesced, this can cause deadlock.\n\nUse memalloc_noio_save/restore() in ufshcd_tx_eqtr() to cover all\nallocations in the TX EQTR call tree, including:\n\n - params->eqtr_record in ufshcd_tx_eqtr()\n\n - eqtr_data in __ufshcd_tx_eqtr()\n\n - params in ufs_qcom_get_rx_fom()\n\nThis is preferred over tagging individual call sites with GFP_NOIO, as it\nautomatically covers any future allocations added anywhere in the call tree\nwithout requiring each caller to be aware of this constraint.\n\n[mkp: fix label as suggested by Bart]",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93057"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/760fc6f0e25a72832c2fcf37ecf5f1b770ec8374"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a28a7d9b3bb116da788ae492c90465ec1a7fa6e8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:59Z"
  }
}