First published: Wed Apr 16 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <prior to [POWERPC] spufs: Fix gang destroy leaks |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-22072 has been categorized with a severity level that indicates a potential risk, depending on the system configuration and exposure.
To fix CVE-2025-22072, you should update your Linux kernel to the version that includes the patch for the gang directory lifetimes.
CVE-2025-22072 affects Linux Kernel versions prior to the fix for the POWERPC spufs gang directory issue.
CVE-2025-22072 involves issues with gang directory lifetimes within the Linux kernel, leading to potential leaks during directory handling.
There is no specific workaround for CVE-2025-22072; applying the patch is the recommended solution.