{"uuid": "67dbbe53-6913-4f88-9f5f-dc3d2f5350d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37828", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/15483", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-37828\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: mcq: Add NULL check in ufshcd_mcq_abort()\n\nA race can occur between the MCQ completion path and the abort handler:\nonce a request completes, __blk_mq_free_request() sets rq->mq_hctx to\nNULL, meaning the subsequent ufshcd_mcq_req_to_hwq() call in\nufshcd_mcq_abort() can return a NULL pointer. If this NULL pointer is\ndereferenced, the kernel will crash.\n\nAdd a NULL check for the returned hwq pointer. If hwq is NULL, log an\nerror and return FAILED, preventing a potential NULL-pointer\ndereference.  As suggested by Bart, the ufshcd_cmd_inflight() check is\nremoved.\n\nThis is similar to the fix in commit 74736103fb41 (\"scsi: ufs: core: Fix\nufshcd_abort_one racing issue\").\n\nThis is found by our static analysis tool KNighter.\n\ud83d\udccf Published: 2025-05-08T06:26:20.135Z\n\ud83d\udccf Modified: 2025-05-08T06:26:20.135Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/d6979fabe812a168d5053e5a41d5a2e9b8afd7bf\n2. https://git.kernel.org/stable/c/7d002f591486f5ef4bc02eb02025a53f931f0eb5\n3. https://git.kernel.org/stable/c/47eec518aef3814f64a5da43df81bdd74d8c0041\n4. https://git.kernel.org/stable/c/4c324085062919d4e21c69e5e78456dcec0052fe", "creation_timestamp": "2025-05-08T07:23:08.000000Z"}