Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-71070

kernel: ublk: clean up user copy references on ublk server exit

Overview

Published
13 Jan 2026
Modified
30 Jul 2026
High CVE
0 Registry packages
9 OS packages
2 Linux distributions
Yes Fix available

Description

In the Linux kernel, the following vulnerability has been resolved:

ublk: clean up user copy references on ublk server exit

If a ublk server process releases a ublk char device file, any requests
dispatched to the ublk server but not yet completed will retain a ref
value of UBLK_REFCOUNT_INIT. Before commit e63d2228ef83 ("ublk: simplify
aborting ublk request"), __ublk_fail_req() would decrement the reference
count before completing the failed request. However, that commit
optimized __ublk_fail_req() to call __ublk_complete_rq() directly
without decrementing the request reference count.
The leaked reference count incorrectly allows user copy and zero copy
operations on the completed ublk request. It also triggers the
WARN_ON_ONCE(refcount_read(&io->ref)) warnings in ublk_queue_reinit()
and ublk_deinit_queue().
Commit c5c5eb24ed61 ("ublk: avoid ublk_io_release() called after ublk
char dev is closed") already fixed the issue for ublk devices using
UBLK_F_SUPPORT_ZERO_COPY or UBLK_F_AUTO_BUF_REG. However, the reference
count leak also affects UBLK_F_USER_COPY, the other reference-counted
data copy mode. Fix the condition in ublk_check_and_reset_active_ref()
to include all reference-counted data copy modes. This ensures that any
ublk requests still owned by the ublk server when it exits have their
reference counts reset to 0.

Source: OX vulnerability database

Severity

7.8 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 1 release · 1 package

fixed 1
linux
debian fixes for CVE-2025-71070
ReleasePackageFixed in
14 linux 6.18.3-1

ubuntu 1 release · 7 packages

fixed 7
linux-oracle-6-17 linux-aws-6-17 linux-azure-6-17 linux-nvidia-6-17 linux-oem-6-17 linux-riscv-6-17 +1
ubuntu fixes for CVE-2025-71070
ReleasePackageFixed in
24.04 linux-oracle-6-17 6.17.0-1011.11~24.04.1
24.04 linux-aws-6-17 +1 6.17.0-1012.12~24.04.1
24.04 linux-azure-6-17 6.17.0-1013.13~24.04.1
24.04 linux-nvidia-6-17 6.17.0-1018.18
24.04 linux-oem-6-17 6.17.0-1020.20
24.04 linux-riscv-6-17 6.17.0-22.22.1~24.04.1

1 more row

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.