nvme-tcp: check the data direction of a C2HData PDU
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0673a2affe45ca76b60de31a83c67b1e60f81bde, 5b115d932f6e769ac80783fb18edd21b0aed256e, 80d56202fbdff8906be6954b2776e5c14a4026f2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0673a2affe45ca76b60de31a83c67b1e60f81bde, 5b115d932f6e769ac80783fb18edd21b0aed256e, 80d56202fbdff8906be6954b2776e5c14a4026f2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In 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] <TASK> [ 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] </TASK> [ 6.927226] ---[ end trace 0000000000000000 ]--- [ 6.927878] nvme nvme0: queue 1 failed to copy request 0x71 data [ 6.928709] nvme nvme0: receive failed: -14
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- —
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.0affected
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before df74950ba6008655d4a977d17df7faf4b6e52b74affected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 980d990f3c0560d7dfbfbf14699651fdf02f26eeaffected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 5b115d932f6e769ac80783fb18edd21b0aed256eaffected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 0673a2affe45ca76b60de31a83c67b1e60f81bdeaffected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 80d56202fbdff8906be6954b2776e5c14a4026f2affected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before b4af7999a998787d5eb6facb5a333e04a4f1d2d9affected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before a0c389b8a495bda1eb719d2503853c924b7a8355affected · git
- 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before f83af377c148f6ad94b41c0e8313f12adf45e1c1affected · git
- before 5.0not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89969Sep 16, 2026 · nvmet-tcp: fix out-of-bounds write when receiving an over-long PDU39Monitor
- ← EarlierCVE-2026-89970Sep 16, 2026 · nvmet-auth: Synchronize timeout work during SQ teardown39Monitor
- Later →CVE-2026-89974Sep 16, 2026 · nvme-fc: fix double free of fabrics options when nvme_add_ctrl() fails30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0673a2affe45ca76b60de31a83c67b1e60f81bde | Vendor (CNA) |
| Linux Linux | 5b115d932f6e769ac80783fb18edd21b0aed256e | Vendor (CNA) |
| Linux Linux | 80d56202fbdff8906be6954b2776e5c14a4026f2 | Vendor (CNA) |
| Linux Linux | 980d990f3c0560d7dfbfbf14699651fdf02f26ee | Vendor (CNA) |
| Linux Linux | a0c389b8a495bda1eb719d2503853c924b7a8355 | Vendor (CNA) |
| Linux Linux | b4af7999a998787d5eb6facb5a333e04a4f1d2d9 | Vendor (CNA) |
| Linux Linux | df74950ba6008655d4a977d17df7faf4b6e52b74 | Vendor (CNA) |
| Linux Linux | f83af377c148f6ad94b41c0e8313f12adf45e1c1 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5b115d932f6e769ac80783fb18edd21b0aed256e
- git.kernel.org/stable/c/80d56202fbdff8906be6954b2776e5c14a4026f2
- git.kernel.org/stable/c/980d990f3c0560d7dfbfbf14699651fdf02f26ee
- git.kernel.org/stable/c/a0c389b8a495bda1eb719d2503853c924b7a8355
- git.kernel.org/stable/c/b4af7999a998787d5eb6facb5a333e04a4f1d2d9
- git.kernel.org/stable/c/df74950ba6008655d4a977d17df7faf4b6e52b74
- git.kernel.org/stable/c/f83af377c148f6ad94b41c0e8313f12adf45e1c1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.