In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers… (CVE-2026-74700)
A use-after-free vulnerability in the Linux kernel's network scheduler (net/sched) was resolved by ensuring the rtnl_lock is always acquired when destroying locked classifiers. The flaw involved a race condition between threads creating different filter types that could lead to a locked classifier being destroyed without holding the necessary lock, causing a use-after-free error detected by KASAN.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's net/sched subsystem arises from a race condition in the tc_new_tfilter function where two threads concurrently create different filter types (u32 and flower) in the same chain and priority. This race leads to a locked classifier being destroyed without holding the rtnl_lock, resulting in a use-after-free condition. The issue was fixed by modifying tcf_proto_destroy() to acquire rtnl_lock around the destroy operation for locked classifiers when rtnl_lock is not already held, preventing unsafe destruction and eliminating the race.
Potential Impact
This vulnerability can cause a use-after-free in the kernel's network scheduler, potentially leading to kernel crashes or memory corruption. The provided proof-of-concept triggered a KASAN slab-use-after-free error, indicating a serious memory safety issue. There is no information about active exploitation in the wild.
Mitigation Recommendations
A fix is available that ensures rtnl_lock is held when destroying locked classifiers in the net/sched subsystem. Users should update their Linux kernel to a version that includes this fix. Since no vendor advisory or patch link is provided, check the official Linux kernel repositories or distributions for the patch corresponding to CVE-2026-74700.
In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers… (CVE-2026-74700)
Description
A use-after-free vulnerability in the Linux kernel's network scheduler (net/sched) was resolved by ensuring the rtnl_lock is always acquired when destroying locked classifiers. The flaw involved a race condition between threads creating different filter types that could lead to a locked classifier being destroyed without holding the necessary lock, causing a use-after-free error detected by KASAN.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's net/sched subsystem arises from a race condition in the tc_new_tfilter function where two threads concurrently create different filter types (u32 and flower) in the same chain and priority. This race leads to a locked classifier being destroyed without holding the rtnl_lock, resulting in a use-after-free condition. The issue was fixed by modifying tcf_proto_destroy() to acquire rtnl_lock around the destroy operation for locked classifiers when rtnl_lock is not already held, preventing unsafe destruction and eliminating the race.
Potential Impact
This vulnerability can cause a use-after-free in the kernel's network scheduler, potentially leading to kernel crashes or memory corruption. The provided proof-of-concept triggered a KASAN slab-use-after-free error, indicating a serious memory safety issue. There is no information about active exploitation in the wild.
Mitigation Recommendations
A fix is available that ensures rtnl_lock is held when destroying locked classifiers in the net/sched subsystem. Users should update their Linux kernel to a version that includes this fix. Since no vendor advisory or patch link is provided, check the official Linux kernel repositories or distributions for the patch corresponding to CVE-2026-74700.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-696w-35hf-m34q
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74700"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f1acd9273b499bc77c
Added to database: 08/22/2026, 22:51:29 UTC
Last enriched: 08/23/2026, 00:23:58 UTC
Last updated: 08/23/2026, 01:32:12 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.