Kernel panic via inconsistent child dequeue
Published Jul 19, 2026 · Updated Jul 19, 2026
Denial of service in the Linux kernel's sch_sfb scheduler allows local users to trigger a kernel panic through a crafted qdisc hierarchy. After a child peek places a packet in the qdisc gso_skb queue, sfb_dequeue calls the child's direct dequeue operation instead of consuming the previously peeked packet. The trigger requires SFB to contain a child using qdisc_peek_dequeued within a parent scheduler, and the bounded consequence is a host-wide crash.
Summary
What happened
Denial of service in the Linux kernel's sch_sfb scheduler allows local users to trigger a kernel panic through a crafted qdisc hierarchy. After a child peek places a packet in the qdisc gso_skb queue, sfb_dequeue calls the child's direct dequeue operation instead of consuming the previously peeked packet. The trigger requires SFB to contain a child using qdisc_peek_dequeued within a parent scheduler, and the bounded consequence is a host-wide crash.
The record
- CVE
- CVE-2026-64012
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 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=2.6.39
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <1b9bc71153b01dbde8045b9edede4240f4f5520e
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <1e70274d3b81de28973bcdbce40a512bcb181ff9
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <6c153d97c100f5b282c424101d8ff63122306997
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <84bfbfc0c48731bcce74cdf4f9c497547ec525e0
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <9ad3288632c859cf84183199832d822e7a70bdae
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <dbc560858da8b77dd9e4ef0cd93d421e0e4d7e0e
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <e125f5980b730c67c92a30cf150ec8c3d6777318
- Affected versionversion=e13e02a3c68d899169c78d9a18689bd73491d59a <e5ea51e5f3fbba41d50cd84a530f33bc1c8f4d57
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