CVE-2025-22071 json
spufs: fix a leak in spufs_create_context()
published 2025-04-16 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-11214
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 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.15
- linux Debian 12 6.1.135-1
- linux Debian 14, Debian 13 6.12.25-1
debian advisories DEBIAN-CVE-2025-22071
- linux Ubuntu 22.04 LTS 5.15.0-142.152
- linux Ubuntu 24.04 LTS 6.8.0-86.87
- linux-aws Ubuntu 22.04 LTS 5.15.0-1086.93
- linux-aws Ubuntu 24.04 LTS 6.8.0-1041.43
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1085.94
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1042.45
- linux-gke Ubuntu 22.04 LTS 5.15.0-1083.89
- linux-gke Ubuntu 24.04 LTS 6.8.0-1038.43
ubuntu advisories UBUNTU-CVE-2025-22071
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/829bd6139968e2e759f3928cf65ad0db1e302fe3 commit
- git.kernel.org/stable/c/410c787d89c92df4215d7b1a338e2c1a8aba6b9b commit
- git.kernel.org/stable/c/c4e72a0d75442237b6f3bcca10a7d81b89376d16 commit
- git.kernel.org/stable/c/a333f223e555d27609f8b45d75a08e8e1d36c432 commit
- git.kernel.org/stable/c/239ea3c34673b3244a499fd65771c47e5bffcbb0 commit
- git.kernel.org/stable/c/d04600f43569d48262e1328eaa1592fcefa2c19c commit
- git.kernel.org/stable/c/5a90b699844a5bb96961e5892e51cc59255444a3 commit
- git.kernel.org/stable/c/4a7448c83e117ed68597952ecaede1cebc4427a7 commit
- git.kernel.org/stable/c/0f5cce3fc55b08ee4da3372baccf4bcd36a98396 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-22071 updated
kernel: spufs: fix a leak in spufs_create_context()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/829bd6139968e2e759f3928cf65ad0db1e302fe3
patch
-
git.kernel.org
/stable/c/410c787d89c92df4215d7b1a338e2c1a8aba6b9b
patch
-
git.kernel.org
/stable/c/c4e72a0d75442237b6f3bcca10a7d81b89376d16
patch
-
git.kernel.org
/stable/c/a333f223e555d27609f8b45d75a08e8e1d36c432
patch
-
git.kernel.org
/stable/c/239ea3c34673b3244a499fd65771c47e5bffcbb0
patch
-
git.kernel.org
/stable/c/d04600f43569d48262e1328eaa1592fcefa2c19c
patch
-
git.kernel.org
/stable/c/5a90b699844a5bb96961e5892e51cc59255444a3
patch
-
git.kernel.org
/stable/c/4a7448c83e117ed68597952ecaede1cebc4427a7
patch
-
git.kernel.org
/stable/c/0f5cce3fc55b08ee4da3372baccf4bcd36a98396
patch
- lists.debian.org /debian-lts-announce/2025/05/msg00045.html
Sources
- CVE List CVE-2025-22071
- NVD CVE-2025-22071
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.