Kernel memory corruption via dangling BFQ queue pointer
Published Mar 27, 2025 · Updated Aug 5, 2026
Use-after-free in the BFQ I/O scheduler in Linux allows local users to access freed kernel memory through block I/O activity. bic_set_bfqq() dereferences and writes through an old bfqq pointer after the queue has been freed because release occurs before the pointer update completes. Exploitation requires low-privileged local access and the affected BFQ path; successful abuse can corrupt kernel memory, expose data, alter system state, or crash the host.
Summary
What happened
Use-after-free in the BFQ I/O scheduler in Linux allows local users to access freed kernel memory through block I/O activity. bic_set_bfqq() dereferences and writes through an old bfqq pointer after the queue has been freed because release occurs before the pointer update completes. Exploitation requires low-privileged local access and the affected BFQ path; successful abuse can corrupt kernel memory, expose data, alter system state, or crash the host.
The record
- CVE
- CVE-2023-52983
- Published
- Mar 27, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 27, 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=094f3d9314d67691cb21ba091c1b528f6e3c4893 <511c922c5bf6c8a166bea826e702336bc2424140
- Affected versionversion=5.15.86 <5.15.93
- Affected versionversion=5533742c7cb1bc9b1f0bf401cc397d44a3a9e07a <7f77f3dab5066a7c9da73d72d1eee895ff84a8d5
- Affected versionversion=6.0.16 <6.1
- Affected versionversion=6.1.2 <6.1.11
- Affected versionversion=64dc8c732f5c2b406cc752e6aaa1bd5471159cab <b600de2d7d3a16f9007fad1bdae82a3951a26af2
- Affected versionversion=761564d93c8265f65543acf0a576b32d66bfa26a <cb1876fc33af26d00efdd473311f1b664c77c44e
- Affected versionversion=b22fd72bfebda3956efc4431b60ddfc0a51e03e0
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