LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22071: spufs: fix a leak in spufs_create_context()

In the Linux kernel, the following vulnerability has been resolved: spufs: fix a leak in spufs_create_context() Leak fixes back in 2008 missed one case - if we are trying to set affinity and spufs_mkdir() fails, we need to drop the reference to neighbor.

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-22071 is a Linux kernel bug in spufs context creation. In one error path, the kernel fails to release a reference after a failed directory creation while setting affinity. The public record does not provide CVSS, practical impact, or evidence of exploitation.

Executive priority

Treat this as a routine kernel maintenance item unless local exposure analysis finds relevant spufs usage or affected unpatched kernels in sensitive environments. There is no cited evidence of exploitation, but kernel bugs should still be resolved through normal patch governance.

Technical view

The flaw is a reference leak in spufs_create_context(). Earlier leak fixes missed the case where affinity is being set and spufs_mkdir() fails, leaving the neighbor reference undropped. Stable kernel commits address the missed cleanup path across multiple maintained branches.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the vulnerable spufs code present. The record lists Linux kernel versions from 2.6.25 and stable branch fixes through 2025. Debian LTS also issued an advisory covering kernel updates.

Exploitation context

The CVE record and supplied references do not report active exploitation. KEV status is false. Public evidence in the bundle describes a kernel reference leak, but does not establish exploitability, attack prerequisites, or real-world abuse.

Researcher notes

Available evidence is narrow: the bug is a missed reference drop in a specific spufs_create_context() failure path. The bundle does not include CVSS, CWE, proof of exploitation, or impact detail beyond the leak description, so validation should focus on kernel branch mapping and patch provenance.

Mitigation direction

  • Apply the relevant upstream stable kernel update or vendor backport.
  • Prioritize vendor kernel packages over manual cherry-picking where possible.
  • Review Debian LTS guidance if using affected Debian LTS kernels.
  • Check vendor advisories for branch-specific fixed package versions.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and images.
  • Map deployed kernels to the affected and fixed versions in vendor advisories.
  • Confirm patched kernels include the referenced stable commits or equivalent backports.
  • Record systems where spufs is present or enabled for exposure review.
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-22071 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
LinuxLinux58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5f, 58119068cb27ef7513f80aff44b62a3a8f40ef5funaffected
LinuxLinux2.6.25, 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.