CVE-2025-37983
Linux kernel qibfs Dentry Leak
Description
In the Linux kernel, the following vulnerability has been resolved: qibfs: fix _another_ leak failure to allocate inode => leaked dentry... this one had been there since the initial merge; to be fair, if we are that far OOM, the odds of failing at that particular allocation are low...
INFO
Published Date :
May 20, 2025, 6:15 p.m.
Last Modified :
May 21, 2025, 8:24 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
Affected Products
The following products are affected by CVE-2025-37983
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-37983.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-37983 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-37983 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 20, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: qibfs: fix _another_ leak failure to allocate inode => leaked dentry... this one had been there since the initial merge; to be fair, if we are that far OOM, the odds of failing at that particular allocation are low... Added Reference https://git.kernel.org/stable/c/24faa6ea274a2b96d0a78a0996c3137c2b2a65f0 Added Reference https://git.kernel.org/stable/c/3c2fde33e3e505dfd1a895d1f24bad650c655e14 Added Reference https://git.kernel.org/stable/c/47ab2caba495c1d6a899d284e541a8df656dcfe9 Added Reference https://git.kernel.org/stable/c/545defa656568c74590317cd30068f85134a8216 Added Reference https://git.kernel.org/stable/c/5d53e88d8370b9ab14dd830abb410d9a2671edb6 Added Reference https://git.kernel.org/stable/c/5e280cce3a29b7fe7b828c6ccd5aa5ba87ceb6b6 Added Reference https://git.kernel.org/stable/c/5fe708c5e3c8b2152c6caaa67243e431a5d6cca3 Added Reference https://git.kernel.org/stable/c/bdb43af4fdb39f844ede401bdb1258f67a580a27
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-37983 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-37983
weaknesses.