Local privilege escalation via fixed-file race
Published Apr 12, 2023 · Updated Feb 13, 2025
Use-after-free in Linux Kernel io_uring 5.7 through 5.17 allows local users to gain elevated privileges through fixed-file operations. io_file_get_fixed reads a fixed-file slot without holding ctx->uring_lock, allowing concurrent unregistration to free the referenced file object. Unprivileged local access is required; successful exploitation executes kernel-context code, while failed attempts can crash the system.
Summary
What happened
Use-after-free in Linux Kernel io_uring 5.7 through 5.17 allows local users to gain elevated privileges through fixed-file operations. io_file_get_fixed reads a fixed-file slot without holding ctx->uring_lock, allowing concurrent unregistration to free the referenced file object. Unprivileged local access is required; successful exploitation executes kernel-context code, while failed attempts can crash the system.
The record
- CVE
- CVE-2023-1872
- Published
- Apr 12, 2023
- Updated
- Feb 13, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 12, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.7 <=5.17
What conditions does exploitation require?
What is affected?
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.
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