Vulnerability · Published Apr 16, 2025 · Assigned by Linux
CVE-2025-22072spufs: fix gang directory lifetimes
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.135-1 | DEBIAN-CVE-2025-22072 |
| Debian:12 | linux | 6.1.135-1 | DSA-5907-1 |
| Debian:13 | linux | 6.12.25-1 | DEBIAN-CVE-2025-22072 |
| Debian:14 | linux | 6.12.25-1 | DEBIAN-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux | 6.8.0-86.87 | USN-7835-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-86.87 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1041.43 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1041.43 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1041.43~22.04.1 | USN-7835-6 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1041.43~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1041.47 | USN-7835-1 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1041.47 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1018.18~24.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1041.47~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1041.47~22.04.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1029.32 | USN-7940-2 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1029.32 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1042.45 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1042.45 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1016.16~24.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1042.45~22.04.1 | USN-7835-3 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1042.45~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1038.43 | USN-7835-3 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1038.43 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1025.28 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1025.28 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | 6.11.0-28.28~24.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-86.87~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-86.87~22.04.1 | USN-7835-4 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1039.39 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1039.39 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1039.39~22.04.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1039.39~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-86.87.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-86.87.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | 6.11.0-1015.16~24.04.2 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-86.87.1~22.04.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-86.87.1~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1041.44 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1041.44 | USN-7835-3 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1012.12 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1041.44~22.04.2 | USN-7835-3 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1041.44~22.04.2 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1041.44.1 | USN-7835-3 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1041.44.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1012.12 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1024.24 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1038.39 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1038.39 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1038.39~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1038.39~22.04.1 | USN-7835-5 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1041.45 | USN-7887-2 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1041.45 | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-86.87~22.04.1 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-22072 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1018.19 | UBUNTU-CVE-2025-22072 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2025-22072 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 877907d37da9694a34adc9dc3e2ce09400148cb5 – before 880e7b3da2e765c1f90c94c0539be039e96c7062877907d37da9694a34adc9dc3e2ce09400148cb5 – before 324f280806aab28ef757aecc18df419676c10ef8877907d37da9694a34adc9dc3e2ce09400148cb5 – before 029d8c711f5e5fe8cf63e8a4a1a140a06e224e45877907d37da9694a34adc9dc3e2ce09400148cb5 – before 903733782f3ae28a2f7fe4dfb47c7fe3e079a528877907d37da9694a34adc9dc3e2ce09400148cb5 – before fc646a6c6d14b5d581f162a7e32999f789e3a3ac877907d37da9694a34adc9dc3e2ce09400148cb5 – before c134deabf4784e155d360744d4a6a835b9de4dd4 |
| Linux | Linux | 2.6.22 |
References
- https://git.kernel.org/stable/c/880e7b3da2e765c1f90c94c0539be039e96c7062
- https://git.kernel.org/stable/c/324f280806aab28ef757aecc18df419676c10ef8
- https://git.kernel.org/stable/c/029d8c711f5e5fe8cf63e8a4a1a140a06e224e45
- https://git.kernel.org/stable/c/903733782f3ae28a2f7fe4dfb47c7fe3e079a528
- https://git.kernel.org/stable/c/fc646a6c6d14b5d581f162a7e32999f789e3a3ac
- https://git.kernel.org/stable/c/c134deabf4784e155d360744d4a6a835b9de4dd4
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html