Kernel memory corruption via proc_lseek use-after-free
Published Aug 22, 2025 · Updated Aug 5, 2026
Use-after-free in affected Linux kernel 6.x branches allows local users to trigger invalid memory access during module removal. proc_reg_open reads pde->proc_ops->proc_lseek directly even though module removal can free that operations table; the fix records proc_lseek availability in stable entry flags instead. Triggering the race requires CAP_SYS_MODULE in the initial user namespace, effectively root privilege, and no stable crash or code-execution outcome is publicly documented.
Summary
What happened
Use-after-free in affected Linux kernel 6.x branches allows local users to trigger invalid memory access during module removal. proc_reg_open reads pde->proc_ops->proc_lseek directly even though module removal can free that operations table; the fix records proc_lseek availability in stable entry flags instead. Triggering the race requires CAP_SYS_MODULE in the initial user namespace, effectively root privilege, and no stable crash or code-execution outcome is publicly documented.
The record
- CVE
- CVE-2025-38653
- Published
- Aug 22, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 22, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <1fccbfbae1dd36198dc47feac696563244ad81d3
- Affected versionversion=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <33c778ea0bd0fa62ff590497e72562ff90f82b13
- Affected versionversion=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <c35b0feb80b48720dfbbf4e33759c7be3faaebb6
- Affected versionversion=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <d136502e04d8853a9aecb335d07bbefd7a1519a8
- Affected versionversion=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <fc1072d934f687e1221d685cf1a49a5068318f34
- Affected versionversion=3f61631d47f115b83c935d0039f95cb68b0c8ab7 <ff7ec8dc1b646296f8d94c39339e8d3833d16c05
- Affected versionversion=6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo