Kernel-memory corruption via NVMe discard retry double-free
Published Jul 29, 2024 · Updated Aug 5, 2026
Double-free in the Linux NVMe host driver allows remote attackers controlling an NVMe-oF peer to corrupt kernel memory during discard retries. nvme_cleanup_cmd frees a request's special payload but fails to clear RQF_SPECIAL_PAYLOAD, so a failed retry cleans the same allocation again. The required retry and cleanup sequence is controlled through the remote NVMe-oF peer, and the resulting corruption can crash or compromise the host.
Summary
What happened
Double-free in the Linux NVMe host driver allows remote attackers controlling an NVMe-oF peer to corrupt kernel memory during discard retries. nvme_cleanup_cmd frees a request's special payload but fails to clear RQF_SPECIAL_PAYLOAD, so a failed retry cleans the same allocation again. The required retry and cleanup sequence is controlled through the remote NVMe-oF peer, and the resulting corruption can crash or compromise the host.
The record
- CVE
- CVE-2024-41073
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 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.10
- Affected versionversion=f9d03f96b988002027d4b28ea1b7a24729a4c9b5 <1b9fd1265fac85916f90b4648de02adccdb7220b
- Affected versionversion=f9d03f96b988002027d4b28ea1b7a24729a4c9b5 <882574942a9be8b9d70d13462ddacc80c4b385ba
- Affected versionversion=f9d03f96b988002027d4b28ea1b7a24729a4c9b5 <ae84383c96d6662c24697ab6b44aae855ab670aa
- Affected versionversion=f9d03f96b988002027d4b28ea1b7a24729a4c9b5 <c5942a14f795de957ae9d66027aac8ff4fe70057
- Affected versionversion=f9d03f96b988002027d4b28ea1b7a24729a4c9b5 <e5d574ab37f5f2e7937405613d9b1a724811e5ad
- Affected versionversion=f9d03f96b988002027d4b28ea1b7a24729a4c9b5 <f3ab45aacd25d957547fb6d115c1574c20964b3b
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