CVE-2026-98811net/sched: cls_api: reclaim an empty proto on the error path
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: reclaim an empty proto on the error path Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down. Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them. This is a follow-up to commit d4e359b3608a ("net/sched: cls_api: fix teardown of an adopted proto on insert-race loss"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place. Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1 flower skip_sw ... action drop` (both fail in fl_hw_replace_filter after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible as a bare `filter protocol ip pref 1 flower chain 0` header in `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 12 days later
· 12 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < 0f005c9b8b2e4c018e598cbaf490f27bebfd3d1f
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < 00ad96ee96760d2f12f8c4b3a43f6c6b742c452f
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < 0fc74e7d97d232095ce64cb45d25f0919df7ad4a
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < 315e4fe65cf02ef052de5e6298c3088e448b7517
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < ebc9611ab154c0cd9f1320e2a73f5e936d7535a9
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < 570141625d212fbbcffb9665cb45c0f04610e61a
- affected 8b64678e0af8f4d62a40149baedebe78503a5255 – < 0bb8eab29b55045281a4963d4557f2776cdf8cfa
- affected 5.1
- unaffected < 5.1
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/0f005c9b8b2e4c018e598cbaf490f27bebfd3d1f (opens in a new tab)
- https://git.kernel.org/stable/c/00ad96ee96760d2f12f8c4b3a43f6c6b742c452f (opens in a new tab)
- https://git.kernel.org/stable/c/0fc74e7d97d232095ce64cb45d25f0919df7ad4a (opens in a new tab)
- https://git.kernel.org/stable/c/315e4fe65cf02ef052de5e6298c3088e448b7517 (opens in a new tab)
- https://git.kernel.org/stable/c/ebc9611ab154c0cd9f1320e2a73f5e936d7535a9 (opens in a new tab)
- https://git.kernel.org/stable/c/570141625d212fbbcffb9665cb45c0f04610e61a (opens in a new tab)
- https://git.kernel.org/stable/c/0bb8eab29b55045281a4963d4557f2776cdf8cfa (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103896 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98811)Record last updated .