LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22072: spufs: fix gang directory lifetimes

In the Linux kernel, the following vulnerability has been resolved: spufs: fix gang directory lifetimes prior to "[POWERPC] spufs: Fix gang destroy leaks" we used to have a problem with gang lifetimes - creation of a gang returns opened gang directory, which normally gets removed when that gets closed, but if somebody has created a context belonging to that gang and kept it alive until the gang got closed, removal failed and we ended up with a leak. Unfortunately, it had been fixed the wrong way. Dentry of gang directory was no longer pinned, and rmdir on close was gone. One problem was that failure of open kept calling simple_rmdir() as cleanup, which meant an unbalanced dput(). Another bug was in the success case - gang creation incremented link count on root directory, but that was no longer undone when gang got destroyed. Fix consists of * reverting the commit in question * adding a counter to gang, protected by ->i_rwsem of gang directory inode. * having it set to 1 at creation time, dropped in both spufs_dir_close() and spufs_gang_close() and bumped in spufs_create_context(), provided that it's not 0. * using simple_recursive_removal() to take the gang directory out when counter reaches zero.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw in PowerPC SPU filesystem gang-directory cleanup can corrupt kernel filesystem bookkeeping when local users create and close affected resources. The supplied CVSS assessment rates the potential impact to confidentiality, integrity, and availability as high. It is not described as remotely exploitable.

Executive priority

Treat this as a high-priority local kernel issue on applicable PowerPC systems, especially shared or multi-user hosts. It is less urgent for systems without spufs exposure or untrusted local users. Establish applicability first, then deploy vendor-supported corrected kernels through normal emergency patch governance.

Technical view

The spufs gang-lifetime implementation could perform an unbalanced dput() after a failed open and fail to decrement the root directory link count after successful gang destruction. The kernel fix restores directory lifetime handling, adds a locked gang reference counter, and recursively removes the directory when that counter reaches zero.

Likely exposure

Likely exposure is limited to Linux systems where the PowerPC spufs functionality is available and reachable by a low-privileged local user. The supplied data identifies Linux versions beginning with 2.6.22 and several later branch versions, but its flattened version list is insufficient to determine exact vulnerable ranges reliably.

Exploitation context

The CVSS vector requires local access, low privileges, low complexity, and no user interaction. The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation or a public exploit. KEV absence alone does not prove exploitation has never occurred.

Researcher notes

The defect concerns dentry and link-count lifetime management rather than a source-described exploitation primitive. The supplied CVSS claims high confidentiality, integrity, and availability impact, but the bundle does not explain how those outcomes are achieved. Exact introduction and fixed-version boundaries should be verified against the linked commits and distribution advisories.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable referenced stable-kernel fix.
  • Consult the Linux distribution's advisory to confirm corrected package versions for each deployed release.
  • Prioritize PowerPC systems exposing spufs to untrusted or low-privileged local users.
  • Reduce untrusted local access until affected systems can be updated.

Validation and detection

  • Inventory kernel versions, architecture, and whether spufs functionality is present or used.
  • Compare deployed kernel sources or vendor packages with the applicable referenced fix commit.
  • Confirm the distribution advisory identifies the installed kernel package as corrected.
  • After updating, verify the intended kernel is running and complete normal regression testing.
Prepared
Confidence
medium
Sources
9

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-22072 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-22072Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinux877907d37da9694a34adc9dc3e2ce09400148cb5, 877907d37da9694a34adc9dc3e2ce09400148cb5, 877907d37da9694a34adc9dc3e2ce09400148cb5, 877907d37da9694a34adc9dc3e2ce09400148cb5, 877907d37da9694a34adc9dc3e2ce09400148cb5, 877907d37da9694a34adc9dc3e2ce09400148cb5unaffected
LinuxLinux2.6.22, 0, 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.