Classifier removal via insert-race ownership confusion
Published Sep 17, 2026 · Updated Sep 17, 2026
Race condition in Linux Kernel 5.1 allows local users to remove active packet classifiers via concurrent filter creation requests. In net/sched/cls_api.c, tc_new_tfilter() retains its creation flag after losing an insertion race, causing error cleanup to unlink the winning request's live classifier. Triggering requires CAP_NET_ADMIN in the relevant network namespace and competing requests at the same chain and priority; the documented consequence is silent classifier removal, not a kernel crash.
Summary
What happened
Race condition in Linux Kernel 5.1 allows local users to remove active packet classifiers via concurrent filter creation requests. In net/sched/cls_api.c, tc_new_tfilter() retains its creation flag after losing an insertion race, causing error cleanup to unlink the winning request's live classifier. Triggering requires CAP_NET_ADMIN in the relevant network namespace and competing requests at the same chain and priority; the documented consequence is silent classifier removal, not a kernel crash.
The record
- CVE
- CVE-2026-90248
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Linux Foundation
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=5.1
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <219c87aeefdcc8c1caf28cc99e9b361ce7393d3a
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <a68e664ddf16ecae6d769d6a2eb356f8abab75c9
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <bbe2fd6d77df630356185406a97317f6aa6a92cf
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <bee2208276c8e0e40a249ffdcf6e5434a79a847c
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <d4e359b3608a0e184bbe8d61a5c3b50d0831c44a
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <dc8b33b819cb02a75936940c120aa669ad89942d
- Affected versionversion=8b64678e0af8f4d62a40149baedebe78503a5255 <df02b6dc136af45e92ee4c86f4aa6c9a60790b1e
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started