Answer in brief
CVE-2026-89481 records a High severity (CVSS 7.5) vulnerability in nvme-tcp: fix host memory disclosure on R2T for a read command. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <a4c3c7310156493797c920b10d8648c07aa05403 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <3b3d27670c0c890ba7cf1bc3614cab61bde6d25c || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <3a0b05145053a5fad1a2ddb4e4d87b07385e63e5 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <6efbc52237facda35d2d874fe1765bb4839275d8 | a4c3c7310156493797c920b10d8648c07aa05403, 3b3d27670c0c890ba7cf1bc3614cab61bde6d25c, 3a0b05145053a5fad1a2ddb4e4d87b07385e63e5, 6efbc52237facda35d2d874fe1765bb4839275d8 |
| Linux/Linuxgeneric | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <49a4dcf57608ebf6432dbcb203ed25e7ed581445 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <bc4013c7cce58d46f792c8c87bc8c8318a70190e || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <a4c3c7310156493797c920b10d8648c07aa05403 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <3b3d27670c0c890ba7cf1bc3614cab61bde6d25c || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <3a0b05145053a5fad1a2ddb4e4d87b07385e63e5 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <6efbc52237facda35d2d874fe1765bb4839275d8 | 49a4dcf57608ebf6432dbcb203ed25e7ed581445, bc4013c7cce58d46f792c8c87bc8c8318a70190e, a4c3c7310156493797c920b10d8648c07aa05403, 3b3d27670c0c890ba7cf1bc3614cab61bde6d25c, 3a0b05145053a5fad1a2ddb4e4d87b07385e63e5, 6efbc52237facda35d2d874fe1765bb4839275d8 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.