System crash via stale io_uring allocation metadata
Published Mar 24, 2023 · Updated Feb 20, 2025
NULL pointer dereference in Linux Kernel 5.19 through 6.3 allows local users to crash the system through io_uring file registration. Fixed-file teardown leaves file_alloc_end and alloc_hint uncleared, so later IORING_FILE_INDEX_ALLOC processing searches a freed NULL bitmap. Local unprivileged access and io_uring availability are required; successful triggering causes a kernel crash without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in Linux Kernel 5.19 through 6.3 allows local users to crash the system through io_uring file registration. Fixed-file teardown leaves file_alloc_end and alloc_hint uncleared, so later IORING_FILE_INDEX_ALLOC processing searches a freed NULL bitmap. Local unprivileged access and io_uring availability are required; successful triggering causes a kernel crash without reported data disclosure or modification.
The record
- CVE
- CVE-2023-1583
- Published
- Mar 24, 2023
- Updated
- Feb 20, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2023CVE publishedPublication date reported by the CVE source.
- Feb 20, 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=affected kernel 5.19, 6.0, 6.1, 6.2, 6.3
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.
Weakness, pattern, technique
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