Kernel compromise via unlocked classifier destruction
Published Aug 22, 2026 · Updated Aug 25, 2026
Use-after-free in Linux kernel 5.1 and later traffic-control classifiers allows local users to crash the kernel or execute kernel code via a race. Concurrent u32 and flower creation at the same chain and priority lets the flower error path drop the last u32_tp reference, so tcf_proto_destroy calls tp->ops->destroy without rtnl_lock while another thread can reuse freed classifier memory. Reaching RTM_NEWTFILTER requires a local low-privileged process able to control two racing threads; successful exploitation can panic the host or gain kernel-level execution.
Summary
What happened
Use-after-free in Linux kernel 5.1 and later traffic-control classifiers allows local users to crash the kernel or execute kernel code via a race. Concurrent u32 and flower creation at the same chain and priority lets the flower error path drop the last u32_tp reference, so tcf_proto_destroy calls tp->ops->destroy without rtnl_lock while another thread can reuse freed classifier memory. Reaching RTM_NEWTFILTER requires a local low-privileged process able to control two racing threads; successful exploitation can panic the host or gain kernel-level execution.
The record
- CVE
- CVE-2026-74700
- Published
- Aug 22, 2026
- Updated
- Aug 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-763, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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=12db03b65c2b90752e4c37666977fd4a1b5f5824 <34e77d8e3570f9df3952496ddb402833695662fd
- Affected versionversion=12db03b65c2b90752e4c37666977fd4a1b5f5824 <a347304b2ca1a5377d5bd2d8a72e4b4f12afe648
- Affected versionversion=12db03b65c2b90752e4c37666977fd4a1b5f5824 <a81f9c44d87fb59d99fce72e29e02cab3a49a1c3
- Affected versionversion=12db03b65c2b90752e4c37666977fd4a1b5f5824 <b648c8a56531aeabd1c14f6b5cf1891e269b3756
- Affected versionversion=12db03b65c2b90752e4c37666977fd4a1b5f5824 <d6222af7274f08e7a1848131dc30319993d8f377
- Affected versionversion=5.1
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