Use-after-free vulnerability in nvme-tcp transport error_recovery work

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000541: nvme-tcp: fix possible use-after-free in transport error_recovery work. Affects Kernel versions < bb0d8fb35c4ff00a503c2c4dca4cce8d102a21c4. 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/IP. NVMe (Non-Volatile Memory Express) is a protocol designed for accessing storage media, such as solid-state drives (SSDs), over a PCI Express (PCIe) bus. The nvme-tcp transport layer allows NVMe commands to be transmitted over TCP/IP networks. This vulnerability affects the error_recovery work in the transport layer.

Vulnerability Detail

The vulnerability in nvme-tcp's transport error_recovery work is a use-after-free issue. A use-after-free vulnerability occurs when a program continues to use a memory object after it has been freed. In this case, the vulnerability arises from improper handling of memory during error recovery in the transport layer. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition.

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 essential to update the Linux Kernel to the fixed version to mitigate the risk.

Conclusion

The use-after-free vulnerability in nvme-tcp's transport error_recovery work can be mitigated by updating the Linux Kernel to version v5.16.11 or later. This update will replace the vulnerable code with the patched version, reducing the risk of exploitation. 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 NVMe over TCP/IP, allowing NVMe commands to be transmitted over TCP/IP networks.

A use-after-free vulnerability occurs when a program continues to use 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 denial-of-service condition.

The impact of this vulnerability could range from arbitrary code execution to a denial-of-service condition. An attacker could potentially exploit this vulnerability to gain unauthorized access or disrupt the normal operation of the system.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.16.11 or later. This will ensure that the vulnerable code is replaced with the patched version.

There is no known workaround for this vulnerability. It is crucial to update the Linux Kernel to the fixed version to mitigate the risk.

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