Answer in brief
CVE-2025-37759 records a Unknown severity vulnerability in ublk: fix handling recovery & reissue in ublk_abort_queue(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8284066946e6d9cc979566ce698fe24e7ca0b31e <ab41bf5a211fbec3a85e025658ed90a911ccb692 || >=8284066946e6d9cc979566ce698fe24e7ca0b31e <caa5c8a2358604f38bf0a4afaa5eacda13763067 || >=8284066946e6d9cc979566ce698fe24e7ca0b31e <5d34a30efac9c9c93e150130caa940c0df6053c1 || >=8284066946e6d9cc979566ce698fe24e7ca0b31e <0a21d259ca4d6310fdfcc0284ebbc000e66cbf70 || >=8284066946e6d9cc979566ce698fe24e7ca0b31e <6ee6bd5d4fce502a5b5a2ea805e9ff16e6aa890f | ab41bf5a211fbec3a85e025658ed90a911ccb692, caa5c8a2358604f38bf0a4afaa5eacda13763067, 5d34a30efac9c9c93e150130caa940c0df6053c1, 0a21d259ca4d6310fdfcc0284ebbc000e66cbf70, 6ee6bd5d4fce502a5b5a2ea805e9ff16e6aa890f |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
May 1, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
In the Linux kernel, the following vulnerability has been resolved: ublk: fix handling recovery & reissue in ublk_abort_queue() Commit 8284066946e6 ("ublk: grab request reference when the request is handled by userspace") doesn't grab request reference in case of recovery reissue. Then the request can be requeued & re-dispatch & failed when canceling uring command. If it is one zc request, the request can be freed before io_uring returns the zc buffer back, then cause kernel panic: [ 126.773061] BUG: kernel NULL pointer dereference, address: 00000000000000c8 [ 126.773657] #PF: supervisor read access in kernel mode [ 126.774052] #PF: error_code(0x0000) - not-present page [ 126.774455] PGD 0 P4D 0 [ 126.774698] Oops: Oops: 0000 [#1] SMP NOPTI [ 126.775034] CPU: 13 UID: 0 PID: 1612 Comm: kworker/u64:55 Not tainted 6.14.0_blk+ #182 PREEMPT(full) [ 126.775676] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-1.fc39 04/01/2014 [ 126.776275] Workqueue: iou_exit io_ring_exit_work [ 126.776651] RIP: 0010:ublk_io_release+0x14/0x130 [ublk_drv] Fixes it by always grabbing request reference for aborting the request.
Quoted source text, attributed separately from HOL analysis.