GHSA-9393-XPW8-3983
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:31In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: check the data direction of a C2HData PDU
nvme_tcp_handle_c2h_data() finds the request by command id and checks that it has a payload, but it does not check that the command asked for data to be read. A controller that answers a write command with C2HData therefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits WARN_ON_ONCE(i->data_source) and returns 0. The receive path turns that into -EFAULT and resets the controller.
No data is copied, so this is not memory corruption. What a controller gets is a kernel warning it can raise at will, which is fatal on a host booted with panic_on_warn.
The send path already knows the direction - it consults rq_data_dir() when it builds a command - and nvme_tcp_handle_r2t() checks the length and the offset of the request it names. The C2HData path does not check the direction at all.
Reject a C2HData PDU whose command is not a read. Rejecting it fails the command and resets the controller, as the neighbouring check in this function does; what goes away is the warning.
[ 6.885580] ------------[ cut here ]------------ [ 6.886457] WARNING: lib/iov_iter.c:193 at _copy_to_iter+0x289/0x1330, CPU#0: kworker/0:1H/71 [ 6.888137] CPU: 0 UID: 0 PID: 71 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy) [ 6.891165] Workqueue: nvme_tcp_wq nvme_tcp_io_work [ 6.891875] RIP: 0010:_copy_to_iter+0x289/0x1330 [ 6.903739] Call Trace: [ 6.904085] [ 6.909254] __skb_datagram_iter+0x433/0x820 [ 6.911026] skb_copy_datagram_iter+0x37/0x120 [ 6.911622] nvme_tcp_recv_skb+0xa07/0x4320 [ 6.913378] __tcp_read_sock+0x1ab/0x810 [ 6.915788] nvme_tcp_try_recv+0x152/0x1e0 [ 6.918222] nvme_tcp_io_work+0x1e4/0x6c0 [ 6.926906] [ 6.927226] ---[ end trace 0000000000000000 ]--- [ 6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data [ 6.928709] nvme nvme0: receive failed: -14
{
"affected": [],
"aliases": [
"CVE-2026-89973"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:17:08Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: check the data direction of a C2HData PDU\n\nnvme_tcp_handle_c2h_data() finds the request by command id and checks\nthat it has a payload, but it does not check that the command asked for\ndata to be read. A controller that answers a write command with C2HData\ntherefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits\nWARN_ON_ONCE(i-\u003edata_source) and returns 0. The receive path turns that\ninto -EFAULT and resets the controller.\n\nNo data is copied, so this is not memory corruption. What a controller\ngets is a kernel warning it can raise at will, which is fatal on a host\nbooted with panic_on_warn.\n\nThe send path already knows the direction - it consults rq_data_dir()\nwhen it builds a command - and nvme_tcp_handle_r2t() checks the length\nand the offset of the request it names. The C2HData path does not check\nthe direction at all.\n\nReject a C2HData PDU whose command is not a read. Rejecting it fails\nthe command and resets the controller, as the neighbouring check in this\nfunction does; what goes away is the warning.\n\n [ 6.885580] ------------[ cut here ]------------\n [ 6.886457] WARNING: lib/iov_iter.c:193 at _copy_to_iter+0x289/0x1330, CPU#0: kworker/0:1H/71\n [ 6.888137] CPU: 0 UID: 0 PID: 71 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy)\n [ 6.891165] Workqueue: nvme_tcp_wq nvme_tcp_io_work\n [ 6.891875] RIP: 0010:_copy_to_iter+0x289/0x1330\n [ 6.903739] Call Trace:\n [ 6.904085] \u003cTASK\u003e\n [ 6.909254] __skb_datagram_iter+0x433/0x820\n [ 6.911026] skb_copy_datagram_iter+0x37/0x120\n [ 6.911622] nvme_tcp_recv_skb+0xa07/0x4320\n [ 6.913378] __tcp_read_sock+0x1ab/0x810\n [ 6.915788] nvme_tcp_try_recv+0x152/0x1e0\n [ 6.918222] nvme_tcp_io_work+0x1e4/0x6c0\n [ 6.926906] \u003c/TASK\u003e\n [ 6.927226] ---[ end trace 0000000000000000 ]---\n [ 6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data\n [ 6.928709] nvme nvme0: receive failed: -14",
"id": "GHSA-9393-xpw8-3983",
"modified": "2026-09-16T15:31:03Z",
"published": "2026-09-16T12:30:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89973"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0673a2affe45ca76b60de31a83c67b1e60f81bde"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5b115d932f6e769ac80783fb18edd21b0aed256e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/80d56202fbdff8906be6954b2776e5c14a4026f2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/980d990f3c0560d7dfbfbf14699651fdf02f26ee"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a0c389b8a495bda1eb719d2503853c924b7a8355"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b4af7999a998787d5eb6facb5a333e04a4f1d2d9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/df74950ba6008655d4a977d17df7faf4b6e52b74"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f83af377c148f6ad94b41c0e8313f12adf45e1c1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.