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-98814 Overview
CVE-2026-98814 is a use-after-free vulnerability in the Linux kernel's NVMe (Non-Volatile Memory Express) subsystem. The flaw affects the command effects log handling for multipath namespace heads in the nvme_core module. Kernel Address Sanitizer (KASAN) reported a slab use-after-free when an I/O passthrough command was issued through a multipath namespace head after the controller path that originally created the head had been removed. The log pointer tied to the released controller remained referenced by nvme_command_effects(), which nvme_cmd_allowed() then dereferenced during ioctl processing.
Critical Impact
Local processes with access to NVMe character devices can trigger memory corruption through passthrough ioctls on multipath devices after controller removal.
Affected Products
- Linux kernel NVMe core driver (nvme_core)
- Systems using NVMe multipath namespace heads
- Kernel builds prior to commits 351d1c4 and 72ece65
Discovery Timeline
- 2026-10-18 - CVE-2026-98814 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-98814
Vulnerability Analysis
The vulnerability resides in nvme_command_effects() within the nvme_core kernel module. The command effects log cache was anchored to the controller that first created a multipath namespace head. When that controller was removed, the backing memory for the log was freed, but the namespace head continued to reference it. Subsequent passthrough ioctls routed through nvme_ns_head_chr_ioctl() reached nvme_user_cmd(), which called nvme_cmd_allowed() and then nvme_command_effects() on freed memory.
KASAN traced the fault with a Read of size 4 at addr ffff888141b14400 originating from nvme_command_effects+0x192/0x200. The upstream fix relocates the log cache to the NVMe subsystem with one entry per command set. Both controllers and namespace heads hold subsystem references, so log pointers remain valid until subsystem release.
Root Cause
The root cause is incorrect object lifetime management between controller teardown and multipath namespace head retention. The command effects log was owned by the controller object, but references to it outlived the owner through the shared namespace head.
Attack Vector
Exploitation requires local access to the NVMe multipath character device and the ability to issue passthrough ioctls. A local user triggers the race by removing or disconnecting the originating controller path while retaining a reference to the multipath head, then issuing an admin or I/O passthrough command.
// Code example not available - refer to upstream kernel commits
// 351d1c47e45b2b35780d0548b1012d7242ba298d and
// 72ece656abd4de8645a421fb482d7a11e6533a45 for the complete fix
Detection Methods for CVE-2026-98814
Indicators of Compromise
- KASAN reports referencing nvme_command_effects or nvme_cmd_allowed in nvme_core
- Kernel oops or panic traces originating from nvme_ns_head_chr_ioctl after controller hot-unplug events
- Unexpected process crashes invoking NVMe passthrough ioctls on /dev/nvmeXnY multipath devices
Detection Strategies
- Enable KASAN on test and staging kernels to surface use-after-free reads in nvme_core call paths
- Audit workloads that combine NVME_IOCTL_IO_CMD or NVME_IOCTL_ADMIN_CMD with controller detach or reset operations
- Correlate dmesg entries containing slab-use-after-free with NVMe subsystem events in centralized log pipelines
Monitoring Recommendations
- Ship kernel ring buffer logs to a centralized data lake and alert on KASAN, BUG:, and nvme_core string matches
- Track NVMe controller add and remove events alongside character-device ioctl activity for anomaly correlation
- Monitor crash telemetry from fleet endpoints for repeated faults in the nvme_core module
How to Mitigate CVE-2026-98814
Immediate Actions Required
- Apply the upstream fix from kernel commits 351d1c47e45b2b35780d0548b1012d7242ba298d and 72ece656abd4de8645a421fb482d7a11e6533a45
- Rebuild or update kernels on hosts using NVMe multipath, including virtualization and storage servers
- Restrict access to NVMe character devices to trusted administrative users via udev and group permissions
Patch Information
The fix moves the command effects log cache from the controller to the NVMe subsystem, with one entry per command set. Both controllers and namespace heads hold subsystem references, keeping log pointers valid until subsystem release. See the Kernel Git Commit 351d1c4 and Kernel Git Commit 72ece65 for implementation details.
Workarounds
- Avoid removing NVMe controller paths while applications hold open file descriptors on multipath head character devices
- Disable NVMe multipath (nvme_core.multipath=N) where multipath functionality is not required
- Limit CAP_SYS_ADMIN and NVMe device access to minimize local exposure to passthrough ioctls
# Restrict NVMe character device access to the disk group
chown root:disk /dev/nvme*
chmod 0660 /dev/nvme*
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

