scsi: ufs: core: Avoid possible memory reclaim deadlock in TX EQTR context

{
  "id": "6b0b8a1b54ed52a6fae8844fe8c9f96ef826ece0b41a0c30d247746aa1f416d9",
  "url": "https://osv.dev/vulnerability/CVE-2026-93057",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "scsi: ufs: core: Avoid possible memory reclaim deadlock in TX EQTR context",
    "summary": "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]",
    "evidence": "osv:CVE-2026-93057",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "7.2.6",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-93057",
      "aliases": [
        "CVE-2026-93057"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "03e5d38e2f985d8d0b0a60508c0b422f664808e3"
                },
                {
                  "fixed": "a28a7d9b3bb116da788ae492c90465ec1a7fa6e8"
                },
                {
                  "fixed": "760fc6f0e25a72832c2fcf37ecf5f1b770ec8374"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93057.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "7.1.0"
                },
                {
                  "fixed": "7.2.6"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-93057.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:44.473003160Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/760fc6f0e25a72832c2fcf37ecf5f1b770ec8374",
        "https://git.kernel.org/stable/c/a28a7d9b3bb116da788ae492c90465ec1a7fa6e8",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93057.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-93057",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93057.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-93057",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 512466,
  "published_at": "2026-09-17T16:10:45.108+00:00"
}