Kernel memory corruption via stale BFQ queue pointer
Published Feb 26, 2025 · Updated Aug 12, 2026
Use-after-free in affected Linux kernel BFQ I/O scheduler releases before 5.18 allows local users to access freed queue memory. bfq_dispatch_request retains the in-service queue pointer while dispatch can expire and free that queue, then dereferences the stale pointer when checking request state or updating statistics. The path requires local I/O on a block device using BFQ, and exploitation can crash the host or compromise kernel execution.
Summary
What happened
Use-after-free in affected Linux kernel BFQ I/O scheduler releases before 5.18 allows local users to access freed queue memory. bfq_dispatch_request retains the in-service queue pointer while dispatch can expire and free that queue, then dereferences the stale pointer when checking request state or updating statistics. The path requires local I/O on a block device using BFQ, and exploitation can crash the host or compromise kernel execution.
The record
- CVE
- CVE-2022-49176
- Published
- Feb 26, 2025
- Updated
- Aug 12, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 12, 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=24bfd19bb7890255693ee5cb6dc100d8d215d00b <080665e2c3cbfc68359b9a348a3546ed9b908e7a
- Affected versionversion=24bfd19bb7890255693ee5cb6dc100d8d215d00b <40b4ba0030e0b02cbacd424ebb9f4c8b0976c786
- Affected versionversion=24bfd19bb7890255693ee5cb6dc100d8d215d00b <5117c9ff4c2ebae0f5c2c262d42a25a8fbc086e6
- Affected versionversion=24bfd19bb7890255693ee5cb6dc100d8d215d00b <5687958bf18f84384d809f521210d0f5deed03b0
- Affected versionversion=24bfd19bb7890255693ee5cb6dc100d8d215d00b <74e610b5ee0d95e751280567100509eb11517efa
- Affected versionversion=24bfd19bb7890255693ee5cb6dc100d8d215d00b <ab552fcb17cc9e4afe0e4ac4df95fc7b30e8490a
- Affected versionversion=24bfd19bb7890255693ee5cb6dc100d8d215d00b <df6e00b1a53c57dca82c63b5ecbcad5452231bc7
- Affected versionversion=4.15
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.
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