Use after free vulnerability in scsi: libfc

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1002193: scsi: libfc: Fix use after free in fc_exch_abts_resp(). Affects Kernel versions < 5cf2ce8967b0d98c8cfa4dc42ef4fcf080f5c836. 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 scsi: libfc is a component of the Linux Kernel that provides support for Fibre Channel (FC) transport protocol. It is responsible for handling FC exchanges and managing FC fabric services. The vulnerability identified in this component can lead to a use after free condition, which occurs when a program continues to use a memory address after it has been freed. This can result in various security issues, including potential code execution or system crashes.

Vulnerability Detail

The use after free vulnerability in fc_exch_abts_resp() function of scsi: libfc can be exploited by an attacker to execute arbitrary code or cause a denial of service (DoS) condition. The vulnerability arises due to improper handling of FC exchanges, leading to a situation where a memory address is accessed after it has been freed. By carefully crafting malicious FC exchanges, an attacker can trigger this vulnerability and potentially gain control over the affected system.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.189 or later. This fix can be obtained by applying commit 5cf2ce8967b0d98c8cfa4dc42ef4fcf080f5c836 from the official Linux Kernel repository. By updating to the patched version, the use after free vulnerability in scsi: libfc will be addressed.

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 apply the provided fix by updating the Linux Kernel to the recommended version.

Conclusion

The use after free vulnerability in scsi: libfc can have severe security implications, including potential code execution or system crashes. It is crucial to update the Linux Kernel to the recommended version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

scsi: libfc is a component of the Linux Kernel that provides support for Fibre Channel (FC) transport protocol. It handles FC exchanges and manages FC fabric services.

A use after free vulnerability occurs when a program continues to use a memory address after it has been freed. This can lead to various security issues, including potential code execution or system crashes.

The vulnerability can be exploited by an attacker to execute arbitrary code or cause a denial of service (DoS) condition. By carefully crafting malicious FC exchanges, an attacker can potentially gain control over the affected system.

To fix this vulnerability, update the Linux Kernel to version v5.4.189 or later by applying commit 5cf2ce8967b0d98c8cfa4dc42ef4fcf080f5c836 from the official Linux Kernel repository.

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

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.189 or later. This fix can be obtained by applying commit 5cf2ce8967b0d98c8cfa4dc42ef4fcf080f5c836 from the official Linux Kernel repository. By updating to the patched version, the use after free vulnerability in scsi: libfc will be addressed.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.