Answer in brief
CVE-2025-38653 records a Unknown severity vulnerability in proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38653 records a Unknown severity vulnerability in proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <c35b0feb80b48720dfbbf4e33759c7be3faaebb6 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <33c778ea0bd0fa62ff590497e72562ff90f82b13 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <fc1072d934f687e1221d685cf1a49a5068318f34 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <d136502e04d8853a9aecb335d07bbefd7a1519a8 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <1fccbfbae1dd36198dc47feac696563244ad81d3 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <ff7ec8dc1b646296f8d94c39339e8d3833d16c05 | c35b0feb80b48720dfbbf4e33759c7be3faaebb6, 33c778ea0bd0fa62ff590497e72562ff90f82b13, fc1072d934f687e1221d685cf1a49a5068318f34, d136502e04d8853a9aecb335d07bbefd7a1519a8, 1fccbfbae1dd36198dc47feac696563244ad81d3, ff7ec8dc1b646296f8d94c39339e8d3833d16c05 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <c35b0feb80b48720dfbbf4e33759c7be3faaebb6 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <33c778ea0bd0fa62ff590497e72562ff90f82b13 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <fc1072d934f687e1221d685cf1a49a5068318f34 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <d136502e04d8853a9aecb335d07bbefd7a1519a8 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <1fccbfbae1dd36198dc47feac696563244ad81d3 || >=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <ff7ec8dc1b646296f8d94c39339e8d3833d16c05 | c35b0feb80b48720dfbbf4e33759c7be3faaebb6, 33c778ea0bd0fa62ff590497e72562ff90f82b13, fc1072d934f687e1221d685cf1a49a5068318f34, d136502e04d8853a9aecb335d07bbefd7a1519a8, 1fccbfbae1dd36198dc47feac696563244ad81d3, ff7ec8dc1b646296f8d94c39339e8d3833d16c05 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.