CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de()
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (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 03de7ff197a3d0e17d0d5c58fdac99a63cba8110, 1d1596d68a6f11d28f677eedf6cf5b17dbfeb491, 4cba73c4c89219beef7685a47374bf88b1022369.
Low priority for now. Upgrade to Linux Linux 03de7ff197a3d0e17d0d5c58fdac99a63cba8110, 1d1596d68a6f11d28f677eedf6cf5b17dbfeb491, 4cba73c4c89219beef7685a47374bf88b1022369 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: fs/proc: fix uaf in proc_readdir_de() Pde is erased from subdir rbtree through rb_erase(), but not set the node to EMPTY, which may result in uaf access. We should use RB_CLEAR_NODE() set the erased node to EMPTY, then pde_subdir_next() will return NULL to avoid uaf access. We found an uaf issue while using stress-ng testing, need to run testcase getdent and tun in the same time. The steps of the issue is as follows: 1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current pde is tun3; 2) in the [time windows] unregister netdevice tun3 and tun2, and erase them from rbtree. erase tun3 first, and then erase tun2. the pde(tun2) will be released to slab; 3) continue to getdent process, then pde_subdir_next() will return pde(tun2) which is released, it will case uaf access. CPU 0 | CPU 1 ------------------------------------------------------------------------- traverse dir /proc/pid/net/dev_snmp6/ | unregister_netdevice(tun->dev) //tun3 tun2 sys_getdents64() | iterate_dir() | proc_readdir() | proc_readdir_de() | snmp6_unregister_dev() pde_get(de); | proc_remove() read_unlock(&proc_subdir_lock); | remove_proc_subtree() | write_lock(&proc_subdir_lock); [time window] | rb_erase(&root->subdir_node, &parent->subdir); | write_unlock(&proc_subdir_lock); read_lock(&proc_subdir_lock); | next = pde_subdir_next(de); | pde_put(de); | de = next; //UAF | rbtree of dev_snmp6 | pde(tun3) / \ NULL pde(tun2)
- Published
- Dec 6, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 3.19affected
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 1d1596d68a6f11d28f677eedf6cf5b17dbfeb491affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before c81d0385500446efe48c305bbb83d47f2ae23a50affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 4cba73c4c89219beef7685a47374bf88b1022369affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 6f2482745e510ae1dacc9b090194b9c5f918d774affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 67272c11f379d9aa5e0f6b16286b9d89b3f76046affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 623bb26127fb581a741e880e1e1a47d79aecb6f8affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 03de7ff197a3d0e17d0d5c58fdac99a63cba8110affected · git
- 710585d4922fd315f2cada8fbe550ae8ed23e994 and later · before 895b4c0c79b092d732544011c3cecaf7322c36a1affected · git
- before 3.19not affected · semver
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-124.31.1.el10_1 | 6.12.0-124.31.1.el10_1 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-124.31.1.el10_1 | 6.12.0-124.31.1.el10_1 |
| AlmaLinux:8 | bpftool | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.100.1.el8_10 | 4.18.0-553.100.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.100.1.rt7.441.el8_10 | 4.18.0-553.100.1.rt7.441.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40269Dec 6, 2025 · ALSA: usb-audio: Fix potential overflow of PCM transfer buffer31Monitor
- ← EarlierCVE-2025-40270Dec 6, 2025 · mm, swap: fix potential UAF issue for VMA readahead31Monitor
- Later →CVE-2025-40272Dec 6, 2025 · mm/secretmem: fix use-after-free race in fault handler31Monitor
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 | 03de7ff197a3d0e17d0d5c58fdac99a63cba8110 | Vendor (CNA) |
| Linux Linux | 1d1596d68a6f11d28f677eedf6cf5b17dbfeb491 | Vendor (CNA) |
| Linux Linux | 4cba73c4c89219beef7685a47374bf88b1022369 | Vendor (CNA) |
| Linux Linux | 623bb26127fb581a741e880e1e1a47d79aecb6f8 | Vendor (CNA) |
| Linux Linux | 67272c11f379d9aa5e0f6b16286b9d89b3f76046 | Vendor (CNA) |
| Linux Linux | 6f2482745e510ae1dacc9b090194b9c5f918d774 | Vendor (CNA) |
| Linux Linux | 895b4c0c79b092d732544011c3cecaf7322c36a1 | Vendor (CNA) |
| Linux Linux | c81d0385500446efe48c305bbb83d47f2ae23a50 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.100.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.100.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.159-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-devel | 0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
+5
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | local | 2026-05-04 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-05-04 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-06-30 |
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.
- Published
- First PoC+148 d
- TodayOct 25, 2026+323 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/1d1596d68a6f11d28f677eedf6cf5b17dbfeb491
- git.kernel.org/stable/c/4cba73c4c89219beef7685a47374bf88b1022369
- git.kernel.org/stable/c/623bb26127fb581a741e880e1e1a47d79aecb6f8
- git.kernel.org/stable/c/67272c11f379d9aa5e0f6b16286b9d89b3f76046
- git.kernel.org/stable/c/6f2482745e510ae1dacc9b090194b9c5f918d774
- git.kernel.org/stable/c/895b4c0c79b092d732544011c3cecaf7322c36a1
- git.kernel.org/stable/c/c81d0385500446efe48c305bbb83d47f2ae23a50
- cert-portal.siemens.com/productcert/html/ssa-253495.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.