Local system crash via stale BFQ queue pointer
Published Oct 21, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux kernel BFQ I/O scheduler allows local users to crash the system through crafted block I/O. During a multi-queue merge chain, bfq_insert_request wrongly assigns the originating bfq_io_cq to an intermediate bfq_queue, leaving bfqq->bic stale after that context is freed. Exploitation requires low-privileged local access, BFQ on a block device, and the merge-chain I/O pattern; the bounded result is a kernel crash.
Summary
What happened
Use-after-free in the Linux kernel BFQ I/O scheduler allows local users to crash the system through crafted block I/O. During a multi-queue merge chain, bfq_insert_request wrongly assigns the originating bfq_io_cq to an intermediate bfq_queue, leaving bfqq->bic stale after that context is freed. Exploitation requires low-privileged local access, BFQ on a block device, and the merge-chain I/O pattern; the bounded result is a kernel crash.
The record
- CVE
- CVE-2024-47706
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE 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=0 <V3.2
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.
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