nvme-tcp: fix host memory disclosure on R2T for a read command
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix host memory disclosure on R2T for a read command nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller. The command then completes normally and nothing is logged. Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers. Reject an R2T for a request that is not a write.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 3f2304f8c6d6ed97849057bd16fee99e434ca796 · fixed in 49a4dcf57608ebf6432dbcb203ed25e7ed581445; From 3f2304f8c6d6ed97849057bd16fee99e434ca796 · fixed in bc4013c7cce58d46f792c8c87bc8c8318a70190e; From 3f2304f8c6d6ed97849057bd16fee99e434ca796 · fixed in a4c3c7310156493797c920b10d8648c07aa05403; From 3f2304f8c6d6ed97849057bd16fee99e434ca796 · fixed in 3b3d27670c0c890ba7cf1bc3614cab61bde6d25c; From 3f2304f8c6d6ed97849057bd16fee99e434ca796 · fixed in 3a0b05145053a5fad1a2ddb4e4d87b07385e63e5; From 3f2304f8c6d6ed97849057bd16fee99e434ca796 · fixed in 6efbc52237facda35d2d874fe1765bb4839275d8
- Linux Linux
5.0
- KernelLinux
From 5.0.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4