{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-93057","id":"CVE-2026-93057","title":"scsi: ufs: core: Avoid possible memory reclaim deadlock in TX EQTR context","description":"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","descriptionLong":"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]","published":"2026-09-17T16:10:45.108Z","updated":"2026-10-28T02:30:44.473003160Z","reserved":"2026-09-17T15:57:05.659Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"03e5d38e2f985d8d0b0a60508c0b422f664808e3","lessThan":"a28a7d9b3bb116da788ae492c90465ec1a7fa6e8","status":"affected","versionType":"git"},{"version":"03e5d38e2f985d8d0b0a60508c0b422f664808e3","lessThan":"760fc6f0e25a72832c2fcf37ecf5f1b770ec8374","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.1","status":"affected"},{"version":"0","lessThan":"7.1","status":"unaffected","versionType":"semver"},{"version":"7.2.6","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/a28a7d9b3bb116da788ae492c90465ec1a7fa6e8","tags":["web"]},{"url":"https://git.kernel.org/stable/c/760fc6f0e25a72832c2fcf37ecf5f1b770ec8374","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/93xxx/CVE-2026-93057.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93057","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00198,"epssPercentile":0.09577,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-93057","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93057","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-93057","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-93057","ok":true,"note":"scored 2026-11-18"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}