Vulnerability in nvme-tcp Package: Possible req->offset Corruption

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1002202: nvme-tcp: fix possible req->offset corruption. Affects Kernel versions >= db5ad6b7f8cdd6d78efef62a1557461d0cbaee54, < ce7723e9cdae4eb3030da082876580f4b2dc0861. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The nvme-tcp package is a component of the Linux Kernel ecosystem. It provides support for NVMe over TCP, allowing remote access to NVMe devices. NVMe (Non-Volatile Memory Express) is a protocol designed for efficient communication between host systems and solid-state drives (SSDs). The nvme-tcp package enables the use of NVMe devices over TCP/IP networks. However, a vulnerability has been discovered in this package that could lead to req->offset corruption.

Vulnerability Detail

The vulnerability in the nvme-tcp package could result in req->offset corruption. This issue was introduced in version v5.8 of the Linux Kernel by commit db5ad6b7f8cdd6d78efef62a1557461d0cbaee54 and was fixed in version v5.15 by commit ce7723e9cdae4eb3030da082876580f4b2dc0861. The impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could potentially lead to security breaches and data corruption. It is crucial to address this vulnerability to ensure the integrity and security of systems utilizing the nvme-tcp package.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

No workaround has been provided for this vulnerability. It is advised to apply the fix mentioned in the 'how_to_fix' section as soon as possible.

Conclusion

The vulnerability in the nvme-tcp package, which could result in req->offset corruption, poses a potential risk to the security and integrity of systems utilizing this package. It is crucial to update the Linux Kernel to version v5.15 or later, or apply the specific fix commit, to address this vulnerability. Failure to do so may leave systems vulnerable to security breaches and data corruption. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The nvme-tcp package is a component of the Linux Kernel ecosystem that enables remote access to NVMe devices over TCP/IP networks.

Req->offset corruption refers to the potential corruption of the 'offset' field in a request structure. This corruption can occur due to the vulnerability in the nvme-tcp package.

The specific details of how this vulnerability can be exploited have not been disclosed. However, if successfully exploited, it could lead to security breaches and data corruption.

There is no evidence to suggest that this vulnerability has been actively exploited in the wild. However, it is important to apply the fix to mitigate any potential risks.

For more details about this vulnerability, including its technical aspects and impact, refer to the provided references link.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback