CVE-2026-89482
nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone
Reported by linux · Published September 11, 2026
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone Commit 25e5cb780e62 ("nvme-tcp: fix possible crash in write_zeroes processing") established that blk_rq_payload_bytes() must not be read without first checking blk_rq_nr_phys_segments(), and recorded the result in nvme_tcp_setup_cmd_pdu() as req->data_len. The receive side was left as it was. The two differ for REQ_OP_WRITE_ZEROES, which has no physical segments but a non-zero blk_rq_bytes(), so setup leaves req->iter untouched while the receive gate lets a C2HData through and nvme_tcp_recv_data() copies into whatever the previous command on that tag left there. The driver-private area is zeroed only when the tag set is allocated. Reproduced with a test target that leaves a residual iterator on a tag and then sends a C2HData for a WRITE_ZEROES command on the same tag: BUG: KASAN: wild-memory-access in _copy_to_iter+0x642/0x1330 Write of size 512 at addr ffe728c2175dfa81 by task kworker/0:1H/103 CPU: 0 UID: 0 PID: 103 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: nvme_tcp_wq nvme_tcp_io_work Call Trace: <TASK> dump_stack_lvl+0x53/0x70 kasan_report+0xce/0x100 ? _copy_to_iter+0x642/0x1330 kasan_check_range+0x105/0x1b0 __asan_memcpy+0x3c/0x60 _copy_to_iter+0x642/0x1330 ? __pfx_sock_has_perm+0x10/0x10 ? worker_thread+0x45b/0xd10 ? __pfx__copy_to_iter+0x10/0x10 ? _raw_spin_lock_bh+0x83/0xe0 ? __pfx__raw_spin_lock_bh+0x10/0x10 __skb_datagram_iter+0xf3/0x820 ? __pfx_simple_copy_to_iter+0x10/0x10 ? __asan_memcpy+0x3c/0x60 ? skb_copy_bits+0x58d/0x830 skb_copy_datagram_iter+0x37/0x120 nvme_tcp_recv_skb+0xa07/0x4320 ? __pfx_nvme_tcp_recv_skb+0x10/0x10 __tcp_read_sock+0x1ab/0x810 ? __pfx_nvme_tcp_recv_skb+0x10/0x10 ? __pfx_lock_sock_nested+0x10/0x10 ? __pfx___tcp_read_sock+0x10/0x10 nvme_tcp_try_recv+0x152/0x1e0 ? __pfx_nvme_tcp_try_recv+0x10/0x10 ? __pfx_mutex_unlock+0x10/0x10 nvme_tcp_io_work+0x1e4/0x6c0 ? __schedule+0x181a/0x49f0 ? __pfx_nvme_tcp_io_work+0x10/0x10 process_one_work+0x633/0x1030 Keep the blk_rq_payload_bytes() test and add req->data_len to it. The old test is what rejects a C2HData naming a tag that is no longer in flight, because blk_update_request() zeroes rq->__data_len on completion; req->data_len and req->curr_bio are driver-private and survive completion, so they cannot stand in for it. Setup initialises the iterator only when both req->curr_bio and req->data_len are set, so the gate now tests the same two.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-livepatch-6.1.188-233.385 | Amazon Linux | 1:1.0-0.amzn2023 |
| bpftool | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel-modules-extra-common | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.18-headers | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel6.12-headers | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| perf | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel-modules-extra | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.18-modules-extra-common | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel-tools | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 25e5cb780e62bde432b401f312bb847edc78b432, 25e5cb780e62bde432b401f312bb847edc78b432, 25e5cb780e62bde432b401f312bb847edc78b432 |
| Linux | Linux | 5.7, 0, 5.10.270 |
| amazon:2023 | kernel-livepatch-6.1.188-233.385 | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| linux | linux_kernel | 5.7, 5.7, 5.7 |
| amazon:2023 | kernel6.12 | 0 |
| Linux | Linux | 7.3, *, 25e5cb780e62bde432b401f312bb847edc78b432 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel-livepatch-6.12.110-135.201 | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
…and 18 more
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (29 in total, the first dated here)
- Sep 12, 2026 Coalition ESS Score
- Sep 18, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-89482
vulnetix vdb fixes CVE-2026-89482
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89482/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart