CVE-2025-22072
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2025
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 877907d37da9694a34adc9dc3e2ce09400148cb5 | affected | git | 880e7b3da2e765c1f90c94c0539be039e96c7062 | Unavailable | None listed |
| 877907d37da9694a34adc9dc3e2ce09400148cb5 | affected | git | 324f280806aab28ef757aecc18df419676c10ef8 | Unavailable | None listed |
| 877907d37da9694a34adc9dc3e2ce09400148cb5 | affected | git | 029d8c711f5e5fe8cf63e8a4a1a140a06e224e45 | Unavailable | None listed |
| 877907d37da9694a34adc9dc3e2ce09400148cb5 | affected | git | 903733782f3ae28a2f7fe4dfb47c7fe3e079a528 | Unavailable | None listed |
| 877907d37da9694a34adc9dc3e2ce09400148cb5 | affected | git | fc646a6c6d14b5d581f162a7e32999f789e3a3ac | Unavailable | None listed |
| 877907d37da9694a34adc9dc3e2ce09400148cb5 | affected | git | c134deabf4784e155d360744d4a6a835b9de4dd4 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 2.6.22 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 2.6.22 | Unavailable | None listed |
| 6.1.134 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.87 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.23 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.13.11 | unaffected | semver | Unavailable | 6.13.* | None listed |
| 6.14.2 | unaffected | semver | Unavailable | 6.14.* | None listed |
| 6.15 | unaffected | original_commit_for_fix | Unavailable | * | None listed |