Use-after-free vulnerability in nvme-tcp

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000351: nvme-tcp: fix possible use-after-free in transport error_recovery work. Affects Kernel versions < 61a26ffd5ad3ece456d74c4c79f7b5e3f440a141. 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 that provides support for NVMe over TCP. NVMe (Non-Volatile Memory Express) is a protocol designed for accessing solid-state drives (SSDs) over a PCI Express (PCIe) bus. The nvme-tcp package enables the use of NVMe devices over a TCP/IP network.

The vulnerability identified in nvme-tcp is a use-after-free issue that occurs during the transport error recovery work. This vulnerability could potentially be exploited by an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition on a vulnerable system.

Vulnerability Detail

The use-after-free vulnerability in nvme-tcp arises from a flaw in the transport error recovery work. When certain error conditions occur during the transport layer, the code may incorrectly free a memory object that is still being referenced. This can lead to a situation where an attacker can manipulate the freed memory to execute arbitrary code or cause a crash.

The impact of this vulnerability depends on the context in which the nvme-tcp package is used. If the package is utilized in a critical system or network infrastructure, an attacker exploiting this vulnerability could potentially gain unauthorized access, compromise data integrity, or disrupt the availability of services.

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

There is no known workaround for this vulnerability. It is strongly advised to apply the recommended fix by updating the Linux Kernel to the patched version.

Conclusion

The use-after-free vulnerability in nvme-tcp can be mitigated by updating the Linux Kernel to version v5.4.181 or later. This vulnerability could potentially be exploited to execute arbitrary code or cause a denial-of-service condition. It is recommended to apply the fix as soon as possible to ensure the security and stability of systems using the nvme-tcp package.

For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

nvme-tcp is a component of the Linux Kernel that enables the use of NVMe devices over a TCP/IP network.

A use-after-free vulnerability occurs when a program continues to reference a memory object after it has been freed. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a crash.

The impact of this vulnerability depends on the context in which the nvme-tcp package is used. If the package is utilized in a critical system or network infrastructure, an attacker exploiting this vulnerability could potentially gain unauthorized access, compromise data integrity, or disrupt the availability of services.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.181 or later. This fix is implemented in commit 61a26ffd5ad3ece456d74c4c79f7b5e3f440a141 of the Linux Kernel source code.

There is no known workaround for this vulnerability. It is strongly advised to apply the recommended fix by updating the Linux Kernel to the patched version.

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