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-1000395: nvme-tcp: fix possible use-after-free in transport error_recovery work. Affects Kernel versions < e192184cf8bce8dd55d619f5611a2eaba996fa05. 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 storage 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 implements the transport layer for NVMe over TCP connections. This vulnerability affects the package and can lead to a use-after-free issue in the transport error_recovery work.

Vulnerability Detail

The use-after-free vulnerability in nvme-tcp arises from a possible memory access issue during the transport error_recovery work. If exploited, an attacker could potentially manipulate freed memory, leading to a variety of consequences such as crashes, privilege escalation, or arbitrary code execution. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been addressed in the Linux Kernel version v5.10.102 by commit e192184cf8bce8dd55d619f5611a2eaba996fa05.

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 specific workaround mentioned for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel to the latest version.

Conclusion

The use-after-free vulnerability in nvme-tcp can have serious security implications if exploited. It is crucial to update the Linux Kernel to the latest version, which includes the necessary fix for this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

nvme-tcp is a component of the Linux Kernel ecosystem that enables NVMe over TCP, allowing remote access to NVMe storage devices.

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed. This can lead to various security issues, including crashes, privilege escalation, or arbitrary code execution.

If exploited, this vulnerability could result in crashes, privilege escalation, or arbitrary code execution.

Yes, this vulnerability has been fixed in the Linux Kernel version v5.10.102 by commit e192184cf8bce8dd55d619f5611a2eaba996fa05.

To update the Linux Kernel, it is recommended to follow the official documentation and guidelines provided by the Linux Kernel community.

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