Kernel memory corruption via post-completion request dereference
Published May 2, 2025 · Updated Aug 5, 2026
Use-after-free in the Linux kernel NVMe target allows remote attackers to corrupt kernel memory during request completion. The nvmet_req_complete function calls a transport's queue_response operation, which can free the request, and then dereferences that released object when passing its submission-queue reference to percpu_ref_put. The NVMe target must process a response through an implementation that frees the request; no concrete effect beyond kernel-memory corruption has been published.
Summary
What happened
Use-after-free in the Linux kernel NVMe target allows remote attackers to corrupt kernel memory during request completion. The nvmet_req_complete function calls a transport's queue_response operation, which can free the request, and then dereferences that released object when passing its submission-queue reference to percpu_ref_put. The NVMe target must process a response through an implementation that frees the request; no concrete effect beyond kernel-memory corruption has been published.
The record
- CVE
- CVE-2023-53116
- Published
- May 2, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.8
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <04c394208831d5e0d5cfee46722eb0f033cd4083
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <6173a77b7e9d3e202bdb9897b23f2a8afe7bf286
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <8ed9813871038b25a934b21ab76b5b7dbf44fc3a
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <a6317235da8aa7cb97529ebc8121cc2a4c4c437a
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <bcd535f07c58342302a2cd2bdd8894fe0872c8a9
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <e5d99b29012bbf0e86929403209723b2806500c1
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <f1d5888a5efe345b63c430b256e95acb0a475642
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <fafcb4b26393870c45462f9af6a48e581dbbcf7e
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