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-1000355: nvme-rdma: fix possible use-after-free in transport error_recovery work. Affects Kernel versions < d411b2a5da68b8a130c23097014434ac140a2ace. 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 Penetration testing for web, API and mobile 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 with minimal CPU overhead. The nvme-rdma package enables NVMe storage devices to be accessed over RDMA, providing improved performance and reduced latency.

Vulnerability Detail

This vulnerability in nvme-rdma is a use-after-free issue that occurs during transport error recovery work. A use-after-free vulnerability arises when a program continues to use a memory location after it has been freed, leading to potential memory corruption and the possibility of an attacker executing arbitrary code or causing a denial-of-service condition. In this case, the vulnerability occurs in the transport error recovery work of nvme-rdma, which could be exploited by an attacker to manipulate memory and potentially gain unauthorized access or disrupt the system.

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 solution is to update the Linux Kernel to the fixed version.

Conclusion

The use-after-free vulnerability in nvme-rdma has been addressed in Linux Kernel version v5.4.181. Users are advised to update their 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 component of the Linux Kernel that enables NVMe storage devices to be accessed over RDMA (Remote Direct Memory Access) transport, providing improved performance and reduced latency.

A use-after-free vulnerability occurs when a program continues to use a memory location after it has been freed, potentially leading to memory corruption and security issues.

This vulnerability in nvme-rdma could be exploited by an attacker to manipulate memory and potentially gain unauthorized access or disrupt the system.

To fix this vulnerability, users should update their Linux Kernel to version v5.4.181 or later.

There are no specific workarounds mentioned for this vulnerability. The recommended solution is to update the Linux Kernel to the fixed 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