Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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)

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Dec 6, 2025
Updated
Oct 15, 2026
EPSS
0.4% · 38th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2025-40271

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.100.1.el8_104.18.0-553.100.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.100.1.rt7.441.el8_104.18.0-553.100.1.rt7.441.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • 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 buffer
    31Monitor
  • ← EarlierCVE-2025-40270Dec 6, 2025 · mm, swap: fix potential UAF issue for VMA readahead
    31Monitor
  • Later →CVE-2025-40272Dec 6, 2025 · mm/secretmem: fix use-after-free race in fault handler
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux03de7ff197a3d0e17d0d5c58fdac99a63cba8110Vendor (CNA)
Linux Linux1d1596d68a6f11d28f677eedf6cf5b17dbfeb491Vendor (CNA)
Linux Linux4cba73c4c89219beef7685a47374bf88b1022369Vendor (CNA)
Linux Linux623bb26127fb581a741e880e1e1a47d79aecb6f8Vendor (CNA)
Linux Linux67272c11f379d9aa5e0f6b16286b9d89b3f76046Vendor (CNA)
Linux Linux6f2482745e510ae1dacc9b090194b9c5f918d774Vendor (CNA)
Linux Linux895b4c0c79b092d732544011c3cecaf7322c36a1Vendor (CNA)
Linux Linuxc81d0385500446efe48c305bbb83d47f2ae23a50Vendor (CNA)
almalinux:bpftool4.18.0-553.100.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.100.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.100.1.rt7.441.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-devel0:4.18.0-553.100.1.rt7.441.el8_10 · Red Hat:enterprise_linux:8::nfvPackage 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.

Public exploit evidence
SourceKindDate
Exploit-DB entrylocal2026-05-04
Proof-of-concept repository on GitHubstars:02026-05-04
Proof-of-concept repository on GitHubstars:12026-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.

  1. Published
  2. First PoC+148 d
  3. TodayOct 25, 2026+323 d
EPSS, last 120 days

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.

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records