CVE-2026-98153

Awaiting Analysis Awaiting Analysis - Queue

Race Condition in Linux Kernel NVMe Subsystem

Publication date: 2026-09-25

Last updated on: 2026-09-30

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: nvme: fix racy access to FDP placement id array nvme_query_fdp_info() is called per-path and therefore prone to races. It populates head->nr_plids/head->plids for fdp registration. But nothing protects that pair from concurrent access - two paths scanning the same namespace can race to populate it. Avoid the race by moving this initialization work to nvme_alloc_ns_head() which is called once per shared namespace.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-09-30

Generated

2026-10-15

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-14

NVD

CVE-2026-98153

EUVD

EUVD-2026-86984

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves a race condition in the NVMe driver. The function nvme_query_fdp_info() populates an array for FDP registration without protection from concurrent access. Two paths scanning the same namespace can race to populate this array, leading to potential data corruption or undefined behavior.

Detection Guidance

This vulnerability involves a race condition in the Linux kernel's NVMe driver. Detection requires checking kernel logs for NVMe-related errors or crashes, particularly during namespace initialization or FDP (Flexible Data Placement) operations. Commands like dmesg | grep -i nvme or journalctl -k | grep -i nvme may help identify issues. Ensure your kernel version is up to date to confirm if the fix is applied.

Impact Analysis

This vulnerability could lead to data corruption or system instability if multiple paths access the same NVMe namespace simultaneously. It may cause crashes, incorrect data handling, or security issues due to race conditions in kernel memory management.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It involves a race condition in the Linux kernel's NVMe driver that could lead to data corruption or undefined behavior in storage operations. Compliance impacts would only occur if such corruption affected protected data, which is not specified in the provided context.

Mitigation Strategies

Update your Linux kernel to the latest stable version where this vulnerability is patched. If immediate patching is not possible, avoid using NVMe namespaces with shared head structures or FDP features until the update is applied. Monitor kernel logs for race conditions or crashes related to NVMe operations.

Hi! I’m here to help you understand CVE-2026-98153. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70