Vulnerability in Kernel: fid refcount leak in v9fs_vfs_atomic_open_dotl

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004284: 9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl. Affects Kernel versions >= 6636b6dcc3db2258cd0585b8078c1c225c4b6dde, < 8bc5412ba1a45edfd1e451874c483c26a097af2b. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between processes, and handles various system operations. The fid refcount leak vulnerability affects the Kernel's v9fs_vfs_atomic_open_dotl function, which is responsible for atomic file opening in the 9P protocol. This vulnerability can potentially lead to a refcount leak in the fid structure, causing resource exhaustion and potential denial-of-service attacks.

Vulnerability Detail

The fid refcount leak vulnerability in v9fs_vfs_atomic_open_dotl was introduced in version v5.11 of the Linux Kernel and fixed in version v5.18.8. When this vulnerability is exploited, it can result in a refcount leak in the fid structure, leading to resource exhaustion. An attacker could potentially trigger this vulnerability by performing a specially crafted operation, causing the fid structure's reference count to increment without decrementing it properly. This can result in the consumption of excessive system resources and potentially lead to a denial-of-service condition. It is important to note that the impact and attack plausibility of this vulnerability have not been proven yet.

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

No specific workaround has been provided for this vulnerability.

Conclusion

The fid refcount leak vulnerability in v9fs_vfs_atomic_open_dotl of the Kernel can lead to resource exhaustion and potential denial-of-service attacks. It is recommended to update the Linux Kernel to version v5.18.8 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can potentially lead to resource exhaustion and denial-of-service attacks by causing a refcount leak in the fid structure.

You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to mitigate any potential risks.

No, only versions starting from v5.11 up to v5.18.7 are affected. The vulnerability has been fixed in version v5.18.8.

There is no evidence of active exploitation of this vulnerability at the time of this report. However, it is crucial to apply the recommended fix to ensure system security.

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