{"uuid": "5d403305-4a62-4c73-a020-dfa096deb81f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37759", "type": "seen", "source": "https://t.me/cvedetector/24216", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37759 - \"ublk Linux Kernel NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37759 \nPublished : May 1, 2025, 1:15 p.m. | 1\u00a0hour, 5\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nublk: fix handling recovery & reissue in ublk_abort_queue()  \n  \nCommit 8284066946e6 (\"ublk: grab request reference when the request is handled  \nby userspace\") doesn't grab request reference in case of recovery reissue.  \nThen the request can be requeued & re-dispatch & failed when canceling  \nuring command.  \n  \nIf it is one zc request, the request can be freed before io_uring  \nreturns the zc buffer back, then cause kernel panic:  \n  \n[  126.773061] BUG: kernel NULL pointer dereference, address: 00000000000000c8  \n[  126.773657] #PF: supervisor read access in kernel mode  \n[  126.774052] #PF: error_code(0x0000) - not-present page  \n[  126.774455] PGD 0 P4D 0  \n[  126.774698] Oops: Oops: 0000 [#1] SMP NOPTI  \n[  126.775034] CPU: 13 UID: 0 PID: 1612 Comm: kworker/u64:55 Not tainted 6.14.0_blk+ #182 PREEMPT(full)  \n[  126.775676] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-1.fc39 04/01/2014  \n[  126.776275] Workqueue: iou_exit io_ring_exit_work  \n[  126.776651] RIP: 0010:ublk_io_release+0x14/0x130 [ublk_drv]  \n  \nFixes it by always grabbing request reference for aborting the request. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"01 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-01T16:30:10.000000Z"}