CVE-2025-38653
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-22

Last updated on: 2025-11-03

Assigner: kernel.org

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-22
Last Modified
2025-11-03
Generated
2026-05-07
AI Q&A
2025-08-22
EPSS Evaluated
2026-05-05
NVD
CVE-2025-38653
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel 6.1.153
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

The vulnerability can lead to a Use-After-Free (UAF) condition in the Linux kernel when removing kernel modules. This could potentially cause system instability, crashes, or allow an attacker to execute arbitrary code with kernel privileges, depending on the exploitation scenario.


Can you explain this vulnerability to me?

This vulnerability in the Linux kernel involves improper handling of the proc_lseek operation in the proc filesystem. Specifically, checking pde->proc_ops->proc_lseek directly can cause a Use-After-Free (UAF) condition during the removal of kernel modules (rmmod). This issue is due to a gap in the proc_reg_open() function following a previous fix, and it has been addressed by applying a similar fix as suggested by AI Viro.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart