Skip to main content
Vulnerability Database/CVE-2026-98725

CVE-2026-98725: Linux Kernel Buffer Overflow Vulnerability

CVE-2026-98725 is a buffer overflow flaw in the Linux kernel nvmet-auth module that causes out-of-bounds writes during authentication challenges. This article covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98725 Overview

CVE-2026-98725 is an out-of-bounds write vulnerability in the Linux kernel's NVMe over Fabrics target authentication code. The flaw resides in nvmet_auth_challenge() within drivers/nvme/target/fabrics-cmd-auth.c. The function receives its output buffer as a void pointer, causing sizeof(*d) to evaluate to 1 under GCC. This undercounts the fixed challenge header by 15 bytes. A short AUTH_RECEIVE buffer passes the size check before the challenge is copied past the end of its allocation, triggering a slab-out-of-bounds write detected by KASAN.

Critical Impact

A remote NVMe-oF client can trigger a heap out-of-bounds write in the kernel target, resulting in memory corruption and potential kernel panic on systems exposing NVMe-oF targets with authentication enabled.

Affected Products

  • Linux kernel versions containing the vulnerable nvmet_auth_challenge() implementation in drivers/nvme/target/fabrics-cmd-auth.c
  • Systems configured as NVMe over Fabrics (NVMe-oF) targets with DH-HMAC-CHAP authentication enabled
  • NVMe-oF transports including TCP (nvmet_tcp), as shown by the KASAN call trace

Discovery Timeline

  • 2026-10-18 - CVE-2026-98725 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-98725

Vulnerability Analysis

The vulnerability is an out-of-bounds write [CWE-787] in the NVMe-oF target authentication path. nvmet_auth_challenge() is responsible for building the authentication challenge response copied into the host's AUTH_RECEIVE buffer. Because the destination buffer parameter is typed as void *, applying sizeof(*d) to it yields 1 byte instead of the actual size of the challenge header structure. This causes the response-size calculation used for validating the caller's buffer to be short by 15 bytes.

When the host supplies an AUTH_RECEIVE buffer sized to the under-counted value, the function proceeds and writes the full challenge payload past the end of the slab allocation. KASAN captured a write of 32 bytes 16 bytes into a 33-byte region, confirming heap corruption adjacent to legitimate kernel objects. The write occurs in nvmet_tcp_io_work worker context, meaning the corruption is reachable from a network peer that can reach the exposed NVMe-oF target.

Root Cause

The root cause is incorrect use of the sizeof operator on a void-typed pointer. The patch replaces the untyped expression with the typed challenge pointer so sizeof resolves to the actual header length. The upstream fixes are tracked across commits 7fd3c36, 8a9b4c0, 9d61131, ef4dfa2, and fa6778e in the stable trees.

Attack Vector

An attacker able to establish an NVMe-oF session with a vulnerable target can issue a crafted AUTH_RECEIVE command whose declared buffer size satisfies the broken check but is smaller than the real challenge payload. The target then writes the challenge past the allocation, corrupting adjacent slab memory. The reproducer in the commit log triggers the condition over nvmet_tcp, so any routable network path to an exposed NVMe-oF TCP listener is sufficient. No synthetic exploit code is published; see the kernel commits referenced above for the authoritative patch diff.

Detection Methods for CVE-2026-98725

Indicators of Compromise

  • KASAN reports of slab-out-of-bounds writes inside nvmet_execute_auth_receive or nvmet_auth_challenge in kernel logs
  • Kernel panics with panic_on_warn originating from the nvmet_tcp_wq workqueue and nvmet_tcp_io_work call chain
  • Unexpected nvmet target crashes or oopses correlated with inbound NVMe-oF authentication traffic

Detection Strategies

  • Audit kernel versions on storage targets and compare against the fixed commits in the stable trees to identify exposure
  • Enable KASAN on test or canary kernels to catch the out-of-bounds write deterministically during fuzzing of the authentication path
  • Monitor NVMe-oF listener ports (default TCP 4420) for unauthenticated or unexpected session attempts to catch probing

Monitoring Recommendations

  • Forward kernel dmesg and journald output to a central log pipeline and alert on KASAN, BUG:, and nvmet_auth strings
  • Track process restarts and connectivity drops on NVMe-oF initiators that may indicate target-side crashes
  • Baseline the set of hosts permitted to connect to NVMe-oF targets and alert on new source addresses

How to Mitigate CVE-2026-98725

Immediate Actions Required

  • Upgrade affected systems to a Linux kernel release that includes one of the stable commits listed in the references
  • Where immediate patching is not possible, restrict network reachability of NVMe-oF target ports to trusted initiators only
  • Disable the nvmet target modules on hosts that do not need to export NVMe namespaces over fabrics

Patch Information

The fix replaces sizeof(*d) on the void output pointer with the correctly typed challenge pointer so the response-size calculation covers the full challenge header. Apply the vendor kernel update that incorporates commits 7fd3c36, 8a9b4c0, 9d61131, ef4dfa2, or fa6778e, depending on your stable branch.

Workarounds

  • Unload the nvmet and transport modules (nvmet_tcp, nvmet_rdma, nvmet_fc) on hosts that are not acting as NVMe-oF targets
  • Firewall NVMe-oF listener ports so only vetted initiator IPs can reach the target
  • Place NVMe-oF traffic on an isolated storage network segment separate from general-purpose client networks
bash
# Example: block NVMe-oF TCP port from untrusted networks and unload target modules
sudo iptables -A INPUT -p tcp --dport 4420 ! -s 10.0.0.0/24 -j DROP
sudo modprobe -r nvmet_tcp
sudo modprobe -r nvmet

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.