Kernel panic via missing abort request reference
Published May 1, 2025 · Updated May 11, 2026
A NULL pointer dereference in the Linux kernel ublk driver allows local users to crash the system during request recovery. During recovery reissue, ublk_abort_queue() fails to acquire a request reference before cancellation, so a zero-copy request can be freed before io_uring returns its buffer. Local access to a ublk zero-copy workload using recovery reissue is required; canceling the io_uring command can dereference invalid state and panic the kernel.
Summary
What happened
A NULL pointer dereference in the Linux kernel ublk driver allows local users to crash the system during request recovery. During recovery reissue, ublk_abort_queue() fails to acquire a request reference before cancellation, so a zero-copy request can be freed before io_uring returns its buffer. Local access to a ublk zero-copy workload using recovery reissue is required; canceling the io_uring command can dereference invalid state and panic the kernel.
The record
- CVE
- CVE-2025-37759
- Published
- May 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.5
- Affected versionversion=8284066946e6d9cc979566ce698fe24e7ca0b31e <0a21d259ca4d6310fdfcc0284ebbc000e66cbf70
- Affected versionversion=8284066946e6d9cc979566ce698fe24e7ca0b31e <5d34a30efac9c9c93e150130caa940c0df6053c1
- Affected versionversion=8284066946e6d9cc979566ce698fe24e7ca0b31e <6ee6bd5d4fce502a5b5a2ea805e9ff16e6aa890f
- Affected versionversion=8284066946e6d9cc979566ce698fe24e7ca0b31e <caa5c8a2358604f38bf0a4afaa5eacda13763067
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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