Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21999: proc: fix UAF in proc_get_inode()

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.23% (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 4b0b8445b6fd41e6f62ac90547a0ea9d348de3fa, 63b53198aff2e4e6c5866a4ff73c7891f958ffa4, 64dc7c68e040251d9ec6e989acb69f8f6ae4a10b; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 6.6.85.1-2.

Low priority for now. Upgrade to Linux Linux 4b0b8445b6fd41e6f62ac90547a0ea9d348de3fa, 63b53198aff2e4e6c5866a4ff73c7891f958ffa4, 64dc7c68e040251d9ec6e989acb69f8f6ae4a10b; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; azl3 kernel 6.6.85.1-2 on Azure Linux 3.0 6.6.85.1-2 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: proc: fix UAF in proc_get_inode() Fix race between rmmod and /proc/XXX's inode instantiation. The bug is that pde->proc_ops don't belong to /proc, it belongs to a module, therefore dereferencing it after /proc entry has been registered is a bug unless use_pde/unuse_pde() pair has been used. use_pde/unuse_pde can be avoided (2 atomic ops!) because pde->proc_ops never changes so information necessary for inode instantiation can be saved _before_ proc_register() in PDE itself and used later, avoiding pde->proc_ops->... dereference. rmmod lookup sys_delete_module proc_lookup_de pde_get(de); proc_get_inode(dir->i_sb, de); mod->exit() proc_remove remove_proc_subtree proc_entry_rundown(de); free_module(mod); if (S_ISREG(inode->i_mode)) if (de->proc_ops->proc_read_iter) --> As module is already freed, will trigger UAF BUG: unable to handle page fault for address: fffffbfff80a702b PGD 817fc4067 P4D 817fc4067 PUD 817fc0067 PMD 102ef4067 PTE 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 26 UID: 0 PID: 2667 Comm: ls Tainted: G Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) RIP: 0010:proc_get_inode+0x302/0x6e0 RSP: 0018:ffff88811c837998 EFLAGS: 00010a06 RAX: dffffc0000000000 RBX: ffffffffc0538140 RCX: 0000000000000007 RDX: 1ffffffff80a702b RSI: 0000000000000001 RDI: ffffffffc0538158 RBP: ffff8881299a6000 R08: 0000000067bbe1e5 R09: 1ffff11023906f20 R10: ffffffffb560ca07 R11: ffffffffb2b43a58 R12: ffff888105bb78f0 R13: ffff888100518048 R14: ffff8881299a6004 R15: 0000000000000001 FS: 00007f95b9686840(0000) GS:ffff8883af100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff80a702b CR3: 0000000117dd2000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> proc_lookup_de+0x11f/0x2e0 __lookup_slow+0x188/0x350 walk_component+0x2ab/0x4f0 path_lookupat+0x120/0x660 filename_lookup+0x1ce/0x560 vfs_statx+0xac/0x150 __do_sys_newstat+0x96/0x110 do_syscall_64+0x5f/0x170 entry_SYSCALL_64_after_hwframe+0x76/0x7e [adobriyan@gmail.com: don't do 2 atomic ops on the common path]

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 3, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 14th percentile

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.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

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

Follow CVE-2025-21999

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.23 and later · before 6.1.132
  • linux linux kernel6.2 and later · before 6.6.85
  • linux linux kernel6.7 and later · before 6.12.21
  • linux linux kernel6.13 and later · before 6.13.9
  • linux linux kernel6.14

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

    • 5.6affected
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before eda279586e571b05dff44d48e05f8977ad05855daffected · git
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before 4b0b8445b6fd41e6f62ac90547a0ea9d348de3faaffected · git
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before 966f331403dc3ed04ff64eaf3930cf1267965e53affected · git
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before 63b53198aff2e4e6c5866a4ff73c7891f958ffa4affected · git
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before ede3e8ac90ae106f0b29cd759aadebc1568f1308affected · git
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before 64dc7c68e040251d9ec6e989acb69f8f6ae4a10baffected · git
    • 97a32539b9568bb653683349e5a76d02ff3c3e2c and later · before 654b33ada4ab5e926cd9c570196fefa7bec7c1dfaffected · git
    • before 5.6not affected · semver
    • 5.10.236 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-570.22.1.el9_65.14.0-570.22.1.el9_6

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-22006Apr 3, 2025 · net: ethernet: ti: am65-cpsw: Fix NAPI registration sequence
    22Monitor
  • ← EarlierCVE-2025-22007Apr 3, 2025 · Bluetooth: Fix error code in chan_alloc_skb_cb()
    22Monitor
  • Later →CVE-2025-22005Apr 3, 2025 · ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().
    22Monitor

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 Linux4b0b8445b6fd41e6f62ac90547a0ea9d348de3faVendor (CNA)
Linux Linux63b53198aff2e4e6c5866a4ff73c7891f958ffa4Vendor (CNA)
Linux Linux64dc7c68e040251d9ec6e989acb69f8f6ae4a10bVendor (CNA)
Linux Linux654b33ada4ab5e926cd9c570196fefa7bec7c1dfVendor (CNA)
Linux Linux966f331403dc3ed04ff64eaf3930cf1267965e53Vendor (CNA)
Linux Linuxeda279586e571b05dff44d48e05f8977ad05855dVendor (CNA)
Linux Linuxede3e8ac90ae106f0b29cd759aadebc1568f1308Vendor (CNA)
azl3 kernel 6.6.82.1-1 on Azure Linux 3.06.6.85.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.85.1-2 on Azure Linux 3.06.6.85.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.05.15.180.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.05.15.180.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.22.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.22.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+20

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.

No history yet (it accumulates with the daily EPSS job).

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)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

All records