CVE-2025-39881: kernfs: Fix UAF in polling when open file is released
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 34d9cafd469c69ad85e6a36b4303c78382cf5c79, 3c9ba2777d6c86025e1ba4186dc5cd930e40ec5f, 7e64474aba78d240f7804f48f2d454dcca78b15f; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 34d9cafd469c69ad85e6a36b4303c78382cf5c79, 3c9ba2777d6c86025e1ba4186dc5cd930e40ec5f, 7e64474aba78d240f7804f48f2d454dcca78b15f; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: kernfs: Fix UAF in polling when open file is released A use-after-free (UAF) vulnerability was identified in the PSI (Pressure Stall Information) monitoring mechanism: BUG: KASAN: slab-use-after-free in psi_trigger_poll+0x3c/0x140 Read of size 8 at addr ffff3de3d50bd308 by task systemd/1 psi_trigger_poll+0x3c/0x140 cgroup_pressure_poll+0x70/0xa0 cgroup_file_poll+0x8c/0x100 kernfs_fop_poll+0x11c/0x1c0 ep_item_poll.isra.0+0x188/0x2c0 Allocated by task 1: cgroup_file_open+0x88/0x388 kernfs_fop_open+0x73c/0xaf0 do_dentry_open+0x5fc/0x1200 vfs_open+0xa0/0x3f0 do_open+0x7e8/0xd08 path_openat+0x2fc/0x6b0 do_filp_open+0x174/0x368 Freed by task 8462: cgroup_file_release+0x130/0x1f8 kernfs_drain_open_files+0x17c/0x440 kernfs_drain+0x2dc/0x360 kernfs_show+0x1b8/0x288 cgroup_file_show+0x150/0x268 cgroup_pressure_write+0x1dc/0x340 cgroup_file_write+0x274/0x548 Reproduction Steps: 1. Open test/cpu.pressure and establish epoll monitoring 2. Disable monitoring: echo 0 > test/cgroup.pressure 3. Re-enable monitoring: echo 1 > test/cgroup.pressure The race condition occurs because: 1. When cgroup.pressure is disabled (echo 0 > cgroup.pressure), it: - Releases PSI triggers via cgroup_file_release() - Frees of->priv through kernfs_drain_open_files() 2. While epoll still holds reference to the file and continues polling 3. Re-enabling (echo 1 > cgroup.pressure) accesses freed of->priv epolling disable/enable cgroup.pressure fd=open(cpu.pressure) while(1) ... epoll_wait kernfs_fop_poll kernfs_get_active = true echo 0 > cgroup.pressure ... cgroup_file_show kernfs_show // inactive kn kernfs_drain_open_files cft->release(of); kfree(ctx); ... kernfs_get_active = false echo 1 > cgroup.pressure kernfs_show kernfs_activate_one(kn); kernfs_fop_poll kernfs_get_active = true cgroup_file_poll psi_trigger_poll // UAF ... end: close(fd) To address this issue, introduce kernfs_get_active_of() for kernfs open files to obtain active references. This function will fail if the open file has been released. Replace kernfs_get_active() with kernfs_get_active_of() to prevent further operations on released file descriptors.
- Published
- Sep 23, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.1affected
- 34f26a15611afb03c33df6819359d36f5b382589 and later · before 34d9cafd469c69ad85e6a36b4303c78382cf5c79affected · git
- 34f26a15611afb03c33df6819359d36f5b382589 and later · before 854baafc00c433cccbe0ab4231b77aeb9b637b77affected · git
- 34f26a15611afb03c33df6819359d36f5b382589 and later · before 7e64474aba78d240f7804f48f2d454dcca78b15faffected · git
- 34f26a15611afb03c33df6819359d36f5b382589 and later · before ac5cda4fae8818cf1963317bb699f7f2f85b60afaffected · git
- 34f26a15611afb03c33df6819359d36f5b382589 and later · before 3c9ba2777d6c86025e1ba4186dc5cd930e40ec5faffected · git
- before 6.1not affected · semver
- 6.1.153 and later · up to and including 6.1.*not affected · semver
- 6.6.107 and later · up to and including 6.6.*not affected · semver
- 6.12.48 and later · up to and including 6.12.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel6.1 and later · before 6.1.153
- linux linux kernel6.2 and later · before 6.6.107
- linux linux kernel6.7 and later · before 6.12.48
- linux linux kernel6.13 and later · before 6.16.8
- linux linux kernel6.17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.42.1.el10_0 | 6.12.0-55.42.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.42.1.el10_0 | 6.12.0-55.42.1.el10_0 |
| Debian:12 | linux | before 6.1.153-1 | 6.1.153-1 |
| Debian:13 | linux | before 6.12.48-1 | 6.12.48-1 |
| Debian:14 | linux | before 6.16.8-1 | 6.16.8-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.6.1.160000.2.4 | 6.12.0-160000.6.1.160000.2.4 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.7.1 | 6.12.0-160000.7.1 |
| Red Hat:enterprise_linux:10.0 | kernel | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-core | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-core | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-debuginfo | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-devel | before 0:6.12.0-55.42.1.el10_0 | 0:6.12.0-55.42.1.el10_0 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39879Sep 23, 2025 · ceph: always call ceph_shift_unused_folios_left()22Monitor
- ← EarlierCVE-2025-39880Sep 23, 2025 · libceph: fix invalid accesses to ceph_connection_v1_info31Monitor
- Later →CVE-2025-39882Sep 23, 2025 · drm/mediatek: fix potential OF node use-after-free31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 34d9cafd469c69ad85e6a36b4303c78382cf5c79 | Vendor (CNA) |
| Linux Linux | 3c9ba2777d6c86025e1ba4186dc5cd930e40ec5f | Vendor (CNA) |
| Linux Linux | 7e64474aba78d240f7804f48f2d454dcca78b15f | Vendor (CNA) |
| Linux Linux | 854baafc00c433cccbe0ab4231b77aeb9b637b77 | Vendor (CNA) |
| Linux Linux | ac5cda4fae8818cf1963317bb699f7f2f85b60af | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel-abi-stablelists | 6.12.0-55.42.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-doc | 6.12.0-55.42.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.153-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.6.1.160000.2.4 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 6.12.0-160000.7.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-55.42.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
+14
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3c9ba2777d6c86025e1ba4186dc5cd930e40ec5f
- git.kernel.org/stable/c/7e64474aba78d240f7804f48f2d454dcca78b15f
- git.kernel.org/stable/c/854baafc00c433cccbe0ab4231b77aeb9b637b77
- git.kernel.org/stable/c/ac5cda4fae8818cf1963317bb699f7f2f85b60af
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.