Completed-request access via leaked ublk reference
Published Jan 13, 2026 · Updated Jan 13, 2026
Reference-count cleanup errors in the Linux kernel ublk driver allow local users to access completed requests after a ublk server exits. The UBLK_REFCOUNT_INIT value survives because __ublk_fail_req() completes outstanding I/O without decrementing or resetting the request reference. A local ublk server process must close its character device with requests pending; user-copy or zero-copy operations can then target requests already marked complete and trigger kernel warnings.
Summary
What happened
Reference-count cleanup errors in the Linux kernel ublk driver allow local users to access completed requests after a ublk server exits. The UBLK_REFCOUNT_INIT value survives because __ublk_fail_req() completes outstanding I/O without decrementing or resetting the request reference. A local ublk server process must close its character device with requests pending; user-copy or zero-copy operations can then target requests already marked complete and trigger kernel warnings.
The record
- CVE
- CVE-2025-71070
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.15
- Affected versionversion=e537193fc4a43b48ac51cc6366319e15e32dd540
- Affected versionversion=e63d2228ef831af36f963b3ab8604160cfff84c1 <13456b4f1033d911f8bf3a0a1195656f293ba0f6
- Affected versionversion=e63d2228ef831af36f963b3ab8604160cfff84c1 <daa24603d9f0808929514ee62ced30052ca7221c
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo