Kernel crash or code execution via BFQ race
Published May 5, 2020 · Updated Aug 4, 2024
Use-after-free in the Linux kernel before 5.6.5 allows local users to crash the system or execute arbitrary code through the BFQ scheduler. bfq_idle_slice_timer reads bfqd->in_service_queue outside bfqd-lock, allowing expiration to free the queue before bfq_idle_slice_timer_body dereferences it. A local low-privileged user must groom memory and win the BFQ scheduler race; successful triggering crashes the kernel or escalates privileges.
Summary
What happened
Use-after-free in the Linux kernel before 5.6.5 allows local users to crash the system or execute arbitrary code through the BFQ scheduler. bfq_idle_slice_timer reads bfqd->in_service_queue outside bfqd-lock, allowing expiration to free the queue before bfq_idle_slice_timer_body dereferences it. A local low-privileged user must groom memory and win the BFQ scheduler race; successful triggering crashes the kernel or escalates privileges.
The record
- CVE
- CVE-2020-12657
- Published
- May 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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