LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22073: spufs: fix a leak on spufs_new_file() failure

In the Linux kernel, the following vulnerability has been resolved: spufs: fix a leak on spufs_new_file() failure It's called from spufs_fill_dir(), and caller of that will do spufs_rmdir() in case of failure. That does remove everything we'd managed to create, but... the problem dentry is still negative. IOW, it needs to be explicitly dropped.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-22073 is a Linux kernel defect in the spufs file-creation path. When setup fails partway through, cleanup misses a negative directory entry, causing a leak. The public record does not provide CVSS, CWE, impact detail, or active exploitation evidence.

Executive priority

Handle through normal kernel patch governance unless affected systems are business-critical or custom-built. There is insufficient evidence for emergency response, but kernel leaks can affect reliability and should not be ignored.

Technical view

The flaw is in spufs_new_file() failure handling, called from spufs_fill_dir(). Existing error cleanup via spufs_rmdir() removes created objects, but the failing dentry remains negative and must be explicitly dropped. Linux stable commits and a Debian LTS advisory reference fixes.

Likely exposure

Exposure appears limited to Linux systems with affected kernel builds containing the spufs code path. The provided record lists Linux kernel versions and stable commits, but does not identify distributions beyond Debian LTS or runtime prerequisites.

Exploitation context

No active exploitation is supported by the bundle. The CVE is not marked KEV, and the supplied sources describe a kernel leak fix rather than exploitation, exploitability, or attacker prerequisites.

Researcher notes

The source evidence is narrow: a kernel commit description, version metadata, and Debian LTS advisory reference. Missing data includes CVSS, CWE, exploitability analysis, attacker requirements, and concrete impact beyond the leaked negative dentry.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • For Debian LTS, review and apply the May 2025 kernel advisory updates.
  • Prioritize systems using affected Linux kernel branches or custom kernels.
  • Check vendor guidance if your distribution is not covered here.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and images.
  • Compare deployed kernels with distribution advisories and fixed stable commits.
  • Confirm whether spufs is present in relevant kernel builds.
  • Verify updated systems boot into the remediated kernel.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22073 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
11Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9e, 3f51dd91c80746a5cf76f8c4a77bfc88aa82bb9eunaffected
LinuxLinux2.6.16, 0, 5.4.292, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.