Local code execution via freeing inode list update
Published Feb 26, 2023 · Updated May 5, 2025
Use-after-free in Linux kernel 6.0.8 allows local users to execute arbitrary code through filesystem writeback operations. writeback_single_inode can update a freeing inode's i_io_list after eviction removes it from the writeback list, leaving the flusher thread to access freed inode memory. Low-privileged local access is required; successful exploitation can crash the system or execute code in kernel context.
Summary
What happened
Use-after-free in Linux kernel 6.0.8 allows local users to execute arbitrary code through filesystem writeback operations. writeback_single_inode can update a freeing inode's i_io_list after eviction removes it from the writeback list, leaving the flusher thread to access freed inode memory. Low-privileged local access is required; successful exploitation can crash the system or execute code in kernel context.
The record
- CVE
- CVE-2023-26605
- Published
- Feb 26, 2023
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1068, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
Public exploit references
- LKML inode writeback use-after-free reproducerproof of concept · unverified
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