CVE-2026-89482ImportantNetworkRevised 2 Oct

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone

MSRC advisory NVD CVE.org

Assessment

Severity: Important
CVSS base score: 7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
Impact: Not stated
EPSS · 30-day forecast: No EPSS score collected
Public detection template: No Nuclei template is listed in the current collected catalog
Exploitation detected: Unknown: not stated by MSRC
Exploitability: Not assessed
Publicly disclosed: Unknown: not stated by MSRC
Customer action: Required: follow the MSRC remediation guidance
Component: Mariner
Weakness: —
Issued by: Linux
Published: 13 Sep 2026 · September 2026
Last revised: 2 Oct 2026Information published.

CVSS 3.1 base metricsRed raises the risk · green lowers it

Attack vector: NetworkAV:N
Attack complexity: HighAC:H
Privileges required: NonePR:N
User interaction: NoneUI:N
Scope: UnchangedS:U
Confidentiality: NoneC:N
Integrity: HighI:H
Availability: HighA:H

Updates that fix it

0 KBs

No KB listed

No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.

Affected products

Open Source Software

2 affected products

azl3 kernel 6.6.150.1-1 on Azure Linux 3.0
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0

What changed

Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
6 Nov 2026 · 17:32:22 UTC
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
6 Nov 2026 · 16:31:02 UTC
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
2 Nov 2026 · 17:30:39 UTC
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
2 Nov 2026 · 16:27:39 UTC
Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
29 Oct 2026
Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
23 Oct 2026 · 09:33:49 UTC
Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
23 Oct 2026 · 08:31:50 UTC

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version

Field-level log (35)

Up to 100 recent field edits are shown; older edits may be outside retention.

6 Nov 2026 · 17:32:22 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
6 Nov 2026 · 17:32:22 UTC Source coverage: public-exploit-codeIncomplete → Current
6 Nov 2026 · 17:32:22 UTC Source coverage: first-epssIncomplete → Current
6 Nov 2026 · 17:32:22 UTC Source coverage: msrc-cvrfIncomplete → Current
6 Nov 2026 · 16:31:02 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
6 Nov 2026 · 16:31:02 UTC Source coverage: public-exploit-codeCurrent → Incomplete
6 Nov 2026 · 16:31:02 UTC Source coverage: first-epssCurrent → Incomplete
6 Nov 2026 · 16:31:02 UTC Source coverage: msrc-cvrfCurrent → Incomplete
2 Nov 2026 · 17:30:39 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
2 Nov 2026 · 17:30:39 UTC Source coverage: public-exploit-codeIncomplete → Current
2 Nov 2026 · 17:30:39 UTC Source coverage: first-epssIncomplete → Current
2 Nov 2026 · 17:30:39 UTC Source coverage: msrc-cvrfIncomplete → Current
2 Nov 2026 · 16:27:39 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
2 Nov 2026 · 16:27:39 UTC Source coverage: public-exploit-codeCurrent → Incomplete
2 Nov 2026 · 16:27:39 UTC Source coverage: first-epssCurrent → Incomplete
2 Nov 2026 · 16:27:39 UTC Source coverage: msrc-cvrfCurrent → Incomplete
29 Oct 2026 · 20:19:26 UTC Public detection templateNo Nuclei template listed
29 Oct 2026 · 20:19:26 UTC EPSSNot scored → No EPSS score collected
29 Oct 2026 · 20:19:26 UTC Customer actionRequired: apply the update → Required: follow the MSRC remediation guidance
29 Oct 2026 · 20:19:26 UTC Publicly disclosedNo → Unknown: not stated by MSRC
29 Oct 2026 · 20:19:26 UTC Exploitation detectedNot reported by MSRC → Unknown: not stated by MSRC
23 Oct 2026 · 09:33:49 UTC Public exploit codeUnknown: exploit-code evidence is incomplete or retained → No Nuclei template listed
23 Oct 2026 · 09:33:49 UTC CISA KEVUnknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
23 Oct 2026 · 09:33:49 UTC Source coverage: public-exploit-codeIncomplete → Current
23 Oct 2026 · 09:33:49 UTC Source coverage: first-epssIncomplete → Current
23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
23 Oct 2026 · 09:33:49 UTC Source coverage: msrc-cvrfIncomplete → Current
23 Oct 2026 · 08:31:50 UTC Public exploit codeNo Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained
23 Oct 2026 · 08:31:50 UTC CISA KEVNot listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
23 Oct 2026 · 08:31:50 UTC Source coverage: public-exploit-codeCurrent → Incomplete
23 Oct 2026 · 08:31:50 UTC Source coverage: first-epssCurrent → Incomplete
23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete
23 Oct 2026 · 08:31:50 UTC Source coverage: msrc-cvrfCurrent → Incomplete
18 Oct 2026 · 14:54:30 UTC Link: September 2026/security?release=2026-Sep#cves
14 Oct 2026 · 11:22:42 UTC Source coverage: msrc-cvrfIncomplete → Current

Explore global source statements, affected packages and advisory history for CVE-2026-89482. The catalog has a separate collection scope from Microsoft release records.

Collected exploitation and prediction evidence

Risk source coverage

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

cve-program · CVE-2026-89482

Published

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone

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.

Source published: 11 Sep 2026 19:43:37 UTC
Source modified: 19 Oct 2026 08:47:32 UTC
Observed here: 23 Oct 2026 15:48:27 UTC
Source terms: CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 3.1 · 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H