Use-after-free vulnerability in nvme-rdma

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1000458: nvme-rdma: fix possible use-after-free in transport error_recovery work. Affects Kernel versions < 646952b2210f19e584d2bf9eb5d092abdca2fcc1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nvme-rdma package is a component of the Linux Kernel that provides support for NVMe over RDMA (Remote Direct Memory Access) transport. RDMA allows for high-speed data transfers between remote systems without involving the CPU. The nvme-rdma package enables NVMe storage devices to communicate with the host system using RDMA. This package is vulnerable to a use-after-free vulnerability in its transport error_recovery work.

Vulnerability Detail

The use-after-free vulnerability in nvme-rdma occurs when the transport error_recovery work is executed. This vulnerability could be exploited by an attacker to manipulate freed memory, leading to a variety of potential security issues. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.15.25 by commit 646952b2210f19e584d2bf9eb5d092abdca2fcc1.

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.

Conclusion

The nvme-rdma package in the Linux Kernel is vulnerable to a use-after-free vulnerability in its transport error_recovery work. This vulnerability has been fixed in Linux Kernel version v5.15.25. It is recommended to update the Linux Kernel to the fixed version to mitigate 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-rdma is a package in the Linux Kernel that enables NVMe storage devices to communicate with the host system using RDMA (Remote Direct Memory Access) transport.

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, data corruption, and potential code execution.

This vulnerability can be exploited by an attacker to manipulate freed memory, potentially leading to security issues such as crashes, data corruption, or even code execution.

No, the impact and attack plausibility of this vulnerability have not been proven yet. However, it is still recommended to apply the fix provided by updating the Linux Kernel to the fixed version.

To fix this vulnerability, update the Linux Kernel to version v5.15.25 or later by pulling the latest changes from the official Linux Kernel repository and checking out the fixed commit. Then, rebuild and install the updated Linux Kernel according to the provided instructions.

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