CVE-2025-38653Published Aug 22, 2025 · Aug 22Updated Oct 28
proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al
Linux
High7.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3f61631d47f115b83c935d0039f95cb68b0c8ab7 · < ff7ec8dc1b646296f8d94c39339e8d3833d16c05| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al
Check pde->proc_ops->proc_lseek directly may cause UAF in rmmod scenario. It's a gap in proc_reg_open() after commit 654b33ada4ab("proc: fix UAF in proc_get_inode()"). Followed by AI Viro's suggestion, fix it in same manner.
From the CVE record · Linux
The Linux kernel's proc_reg_open() can check proc_lseek through a freed pointer during module removal (rmmod). The input does not specify what an attacker could achieve or whether authentication or user interaction is required.
Teams running the Linux kernel should check their deployments; affected versions are not specified.