In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone Commit… (CVE-2026-89482)
A vulnerability in the Linux kernel's nvme-tcp driver was resolved that could cause a kernel crash due to improper handling of C2HData for WRITE_ZEROES commands. The issue arises because the receive side accepted data based solely on blk_rq_payload_bytes() without verifying blk_rq_nr_phys_segments(), leading to a wild memory access. This could result in a kernel crash (KASAN detected) when copying data to an uninitialized iterator. The fix ensures that both req->curr_bio and req->data_len are checked before accepting C2HData, preventing use-after-free or invalid memory access.
AI Analysis
Technical Summary
The Linux kernel nvme-tcp driver had a flaw where it accepted C2HData packets based only on blk_rq_payload_bytes(), ignoring blk_rq_nr_phys_segments(). For REQ_OP_WRITE_ZEROES commands, which have no physical segments but a non-zero byte count, this caused the receive side to copy data into an uninitialized iterator, leading to wild memory access and kernel crashes detected by KASAN. The patch added a check for req->data_len alongside req->curr_bio before accepting C2HData, aligning the receive side with the setup side and preventing invalid memory operations.
Potential Impact
This vulnerability could cause kernel crashes due to wild memory access when processing certain NVMe TCP commands, potentially leading to denial of service. There is no indication of privilege escalation or data corruption beyond the crash. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding proper checks before accepting C2HData. Users should update to a kernel version that includes the commit 25e5cb780e62 or later containing this fix. Patch status is not explicitly confirmed in the input data; therefore, verify with the official Linux kernel advisory or source repository for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone Commit… (CVE-2026-89482)
Description
A vulnerability in the Linux kernel's nvme-tcp driver was resolved that could cause a kernel crash due to improper handling of C2HData for WRITE_ZEROES commands. The issue arises because the receive side accepted data based solely on blk_rq_payload_bytes() without verifying blk_rq_nr_phys_segments(), leading to a wild memory access. This could result in a kernel crash (KASAN detected) when copying data to an uninitialized iterator. The fix ensures that both req->curr_bio and req->data_len are checked before accepting C2HData, preventing use-after-free or invalid memory access.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel nvme-tcp driver had a flaw where it accepted C2HData packets based only on blk_rq_payload_bytes(), ignoring blk_rq_nr_phys_segments(). For REQ_OP_WRITE_ZEROES commands, which have no physical segments but a non-zero byte count, this caused the receive side to copy data into an uninitialized iterator, leading to wild memory access and kernel crashes detected by KASAN. The patch added a check for req->data_len alongside req->curr_bio before accepting C2HData, aligning the receive side with the setup side and preventing invalid memory operations.
Potential Impact
This vulnerability could cause kernel crashes due to wild memory access when processing certain NVMe TCP commands, potentially leading to denial of service. There is no indication of privilege escalation or data corruption beyond the crash. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by adding proper checks before accepting C2HData. Users should update to a kernel version that includes the commit 25e5cb780e62 or later containing this fix. Patch status is not explicitly confirmed in the input data; therefore, verify with the official Linux kernel advisory or source repository for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m28h-7j27-xfqp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89482"]
Threat ID: 6aa4a01955bf5e2cf5a8670a
Added to database: 09/12/2026, 00:43:05 UTC
Last enriched: 09/12/2026, 01:14:03 UTC
Last updated: 09/12/2026, 01:14:03 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.