{
  "cveId": "CVE-2026-93057",
  "url": "https://patchblox.com/security/cve/CVE-2026-93057",
  "summary": "CVE-2026-93057 is fixed in linux on 1 platform by DEBIAN-CVE-2026-93057 (version 7.2.6-1), released September 23, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  scsi: ufs: core: Avoid possible memory reclaim d...",
  "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-\u003Eeqtr_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]",
  "published": "2026-09-17T17:17:59Z",
  "severity": "",
  "epss": 0.00198,
  "epssPercentile": 0.09577,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.2.6-1",
      "fix": "DEBIAN-CVE-2026-93057",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-93057",
      "released": "2026-09-23T19:19:02Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T00:53:09Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}