CVE-2025-40271

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-07. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Elevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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)

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

December 6, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Jul 31, 2026
No patch confirmed yet.
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c81d0385500446efe48c305bbb83d47f2ae23a50
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/895b4c0c79b092d732544011c3cecaf7322c36a1
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f2482745e510ae1dacc9b090194b9c5f918d774
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67272c11f379d9aa5e0f6b16286b9d89b3f76046
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/623bb26127fb581a741e880e1e1a47d79aecb6f8
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4cba73c4c89219beef7685a47374bf88b1022369
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d1596d68a6f11d28f677eedf6cf5b17dbfeb491
generic

fs/proc: fix uaf in proc_readdir_de() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03de7ff197a3d0e17d0d5c58fdac99a63cba8110

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-05-21ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1103.93) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1102.106) @ jammy2026-05-21ubuntu
redhatkernel-rt-0:3.10.0-1160.147.1.rt56.1299.el72026-03-03redhat
redhatkernel-0:3.10.0-1160.147.1.el72026-03-03redhat
redhatkernel-0:4.18.0-193.187.1.el8_22026-02-26redhat
redhatkernel-0:4.18.0-372.181.1.el8_62026-02-25redhat
redhatkernel-0:5.14.0-284.158.1.el9_22026-02-25redhat
redhatkernel-rt-0:5.14.0-70.167.1.rt21.239.el9_02026-02-25redhat
redhatkernel-0:4.18.0-477.130.1.el8_82026-02-25redhat
redhatkernel-0:5.14.0-70.167.1.el9_02026-02-25redhat
redhatkernel-0:4.18.0-305.186.1.el8_42026-02-25redhat
redhatkernel-rt-0:5.14.0-284.158.1.rt14.443.el9_22026-02-25redhat
redhatkernel-0:5.14.0-427.111.1.el9_42026-02-17redhat
redhatkernel-0:5.14.0-570.89.1.el9_62026-02-16redhat
redhatkernel-0:6.12.0-55.60.1.el10_02026-02-16redhat
redhatkernel-0:5.14.0-611.30.1.el9_72026-02-09redhat
redhatkernel-rt-0:4.18.0-553.100.1.rt7.441.el8_102026-02-02redhat
redhatkernel-0:6.12.0-124.31.1.el10_12026-02-02redhat
redhatkernel-0:4.18.0-553.100.1.el8_102026-02-02redhat
linuxKernel @ 5.4.302osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)5.10.247-1
linux-6.16.1.106-3~deb11u1 ... 6.1.158-1~deb11u1 (13 versions)6.1.159-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (45 versions)6.1.159-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)6.12.63-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (77 versions)6.17.9-1

Additional Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 4× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-06 13:46 UTCEPSS rescore
  3. 2026-09-04 05:05 UTCEPSS rescore
  4. 2026-09-02 14:11 UTCEPSS rescore
  5. 2026-09-01 13:53 UTCEPSS rescore
  6. 2026-09-01 04:38 UTCEPSS rescore
  7. 2026-08-30 19:16 UTCEPSS rescore
  8. 2026-08-30 01:21 UTCEPSS rescore
  9. 2026-08-28 21:40 UTCEPSS rescore
  10. 2026-08-27 14:24 UTCEPSS rescore
  11. 2026-08-26 14:45 UTCEPSS rescore
  12. 2026-08-25 13:48 UTCEPSS rescore
  13. 2026-08-24 12:32 UTCOSV refresh
  14. 2026-08-23 00:18 UTCEPSS rescore
  15. 2026-08-21 23:48 UTCEPSS rescore
  16. 2026-08-20 22:54 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 13:47 UTCEPSS rescore
  20. 2026-08-17 13:46 UTCEPSS rescore
  21. 2026-08-16 14:55 UTCEPSS rescore
  22. 2026-08-16 02:13 UTCEPSS rescore
  23. 2026-08-15 01:29 UTCEPSS rescore
  24. 2026-08-13 21:59 UTCEPSS rescore
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-08 16:36 UTCEPSS rescore
  3. 2026-08-08 08:23 UTCEG score recompute
  4. 2026-08-08 08:23 UTCVendor advisory
  5. 2026-08-08 08:23 UTCGHSA enrichment
  6. 2026-08-07 16:26 UTCEPSS rescore
  7. 2026-08-06 13:46 UTCEPSS rescore
  8. 2026-08-05 12:51 UTCEG score recompute
  9. 2026-08-05 12:51 UTCVendor advisory
  10. 2026-08-05 12:51 UTCGHSA enrichment
  11. 2026-08-04 15:09 UTCEPSS rescore
  12. 2026-08-04 10:37 UTCEPSS rescore
  13. 2026-08-03 10:35 UTCEPSS rescore
  14. 2026-08-02 02:26 UTCEPSS rescore
  15. 2026-08-01 04:15 UTCEPSS rescore
  16. 2026-07-30 16:27 UTCEPSS rescore
  17. 2026-07-30 06:25 UTCEG score recompute 7.80
  18. 2026-07-30 06:25 UTCVendor advisory
  19. 2026-07-30 06:25 UTCGHSA enrichment
  20. 2026-07-30 06:18 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  21. 2026-07-30 01:29 UTCEPSS rescore
  22. 2026-07-28 15:35 UTCEPSS rescore
  23. 2026-07-27 06:09 UTCOSV refresh
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-25 14:17 UTCEPSS rescore
  26. 2026-07-25 14:17 UTCEPSS rescore
  27. 2026-07-24 14:17 UTCEPSS rescore
  28. 2026-07-23 02:55 UTCEG score recompute
  29. 2026-07-22 14:07 UTCEPSS rescore
  30. 2026-07-22 14:07 UTCEPSS rescore
  31. 2026-07-21 15:24 UTCEPSS rescore
  32. 2026-07-20 17:07 UTCEPSS rescore
  33. 2026-07-19 14:30 UTCEPSS rescore
  34. 2026-07-19 14:30 UTCEPSS rescore
  35. 2026-07-19 02:28 UTCEPSS rescore
  36. 2026-07-19 02:28 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-16 17:02 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 16:57 UTCEPSS rescore
  42. 2026-07-15 01:59 UTCEPSS rescore
  43. 2026-07-15 01:59 UTCEPSS rescore
  44. 2026-07-13 22:29 UTCEPSS rescore
  45. 2026-07-13 22:29 UTCEPSS rescore
  46. 2026-07-13 06:12 UTCEPSS rescore
  47. 2026-07-12 05:46 UTCEPSS rescore
  48. 2026-07-11 08:27 UTCEPSS rescore
  49. 2026-07-11 08:27 UTCEPSS rescore
  50. 2026-07-10 00:47 UTCOSV refresh
  51. 2026-07-09 19:09 UTCEPSS rescore
  52. 2026-07-09 19:09 UTCEPSS rescore
  53. 2026-07-07 13:45 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 16:27 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-05 02:30 UTCEPSS rescore
  58. 2026-07-04 06:30 UTCEPSS rescore
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-07-01 15:06 UTCEPSS rescore
  61. 2026-06-30 23:22 UTCEPSS rescore
  62. 2026-06-30 23:22 UTCEPSS rescore
  63. 2026-06-29 14:06 UTCEPSS rescore
  64. 2026-06-29 14:06 UTCEPSS rescore
  65. 2026-06-28 14:07 UTCEPSS rescore
  66. 2026-06-28 14:07 UTCEPSS rescore
  67. 2026-06-28 04:55 UTCEPSS rescore
  68. 2026-06-28 04:55 UTCEPSS rescore
  69. 2026-06-27 03:08 UTCEPSS rescore
  70. 2026-06-27 03:08 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-25 13:49 UTCEPSS rescore
  73. 2026-06-24 14:04 UTCEPSS rescore
  74. 2026-06-24 14:04 UTCEPSS rescore
  75. 2026-06-23 21:32 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52550
    First seen May 4, 2026

    Linux Kernel proc_readdir_de() 6.18-rc5 - Local Privilege Escalation

    Open source ↗

Frequently asked(5)

What is CVE-2025-40271?
CVE-2025-40271 is a high vulnerability published on December 6, 2025. In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix uaf in procreaddirde() 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 RBCLEARNODE() set the erased node to EMPTY, then pdesubdirnext()…
When was CVE-2025-40271 disclosed?
CVE-2025-40271 was first published in the National Vulnerability Database on December 6, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40271 actively exploited?
CVE-2025-40271 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.9% of all scored CVEs.
What is the CVSS score of CVE-2025-40271?
CVE-2025-40271 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40271, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-40271

Explore →

Is Your Infrastructure Affected by CVE-2025-40271?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.