{"uuid": "ba0426ff-6d89-44e5-88ca-f0f27112bd2f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37828", "type": "seen", "source": "https://t.me/cvedetector/24790", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37828 - \"ufs Linux Kernel NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37828 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:44:44.000000Z"}