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-1002405: scsi: libfc: Fix use after free in fc_exch_abts_resp(). Affects Kernel versions < 499d198494e77b6533251b9b909baf5c101129cb. 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 the Fibre Channel (FC) transport layer for SCSI commands. It is responsible for handling FC exchanges and managing FC fabric services. The vulnerability identified in this component is a use after free issue, which occurs when a program continues to use a memory address after it has been freed. This can lead to various security implications, including potential remote code execution or denial of service attacks.

Vulnerability Detail

The use after free vulnerability in fc_exch_abts_resp() function of scsi: libfc allows an attacker to exploit a freed memory address, potentially leading to arbitrary code execution or denial of service. The vulnerability arises due to improper handling of FC exchanges, where a response is sent for an aborted exchange. By manipulating the timing of the exchange and the response, an attacker can trigger the use after free condition and potentially execute malicious code or crash 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

As a workaround, users can apply the patch manually by identifying the affected code in fc_exch_abts_resp() function and modifying it to ensure proper memory handling. However, it is highly recommended to update the kernel to the patched version rather than relying on manual modifications.

Conclusion

The use after free vulnerability in scsi: libfc can have serious security implications, including potential remote code execution or denial of service attacks. It is crucial to update the Linux Kernel to version v4.14.276 or later to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

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 implications, including potential remote code execution or denial of service attacks.

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

The use after free vulnerability in scsi: libfc can potentially allow an attacker to execute arbitrary code or cause a denial of service by manipulating FC exchanges and responses.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.14.276 or later, which includes the necessary patch to address the use after free issue.

Yes, a workaround involves manually modifying the affected code in fc_exch_abts_resp() function to ensure proper memory handling. However, it is strongly advised to update the kernel to the patched version instead.

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