Invalid kernel-memory read via premature namespace release
Published May 3, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux kernel NVMe target allows local users to trigger an invalid kernel-memory read during loopback I/O completion. The __nvmet_req_complete function released the namespace before queue_response handled the completed request, allowing the response path to use namespace-backed request state after release. The demonstrated trigger requires a locally configured NVMe loop target and the blktests nvme/004 workload; published evidence establishes neither a remote path nor code execution.
Summary
What happened
Use-after-free in the Linux kernel NVMe target allows local users to trigger an invalid kernel-memory read during loopback I/O completion. The __nvmet_req_complete function released the namespace before queue_response handled the completed request, allowing the response path to use namespace-backed request state after release. The demonstrated trigger requires a locally configured NVMe loop target and the blktests nvme/004 workload; published evidence establishes neither a remote path nor code execution.
The record
- CVE
- CVE-2022-48697
- Published
- May 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 2024CVE 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 <17f121ca3ec6be0fb32d77c7f65362934a38cc8e
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <4484ce97a78171668c402e0c45db7f760aea8060
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <6a02a61e81c231cc5c680c5dbf8665275147ac52
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <8d66989b5f7bb28bba2f8e1e2ffc8bfef4a10717
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <be01f1c988757b95f11f090a9f491365670a522b
- Affected versionversion=a07b4970f464f13640e28e16dad6cfa33647cc99 <ebf46da50beb78066674354ad650606a467e33fa
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
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