{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98811 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98811 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98811 and fix it if it is affected.\n\nWhat it is: CVE-2026-98811 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98811 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98811/ (Markdown: https://insights.sbomify.com/CVE-2026-98811/index.md)","id":"CVE-2026-98811","markdown":"https://insights.sbomify.com/CVE-2026-98811/index.md","name":"CVE-2026-98811","record":{"aliases":["AZL-109377","BELL-CVE-2026-98811","DEBIAN-CVE-2026-98811","GHSA-8rvg-cc82-cvp9","UBUNTU-CVE-2026-98811"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's traffic control classifier allows local attackers to leak kernel memory and references, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_api: reclaim an empty proto on the error path\n\nTwo racing tc filter add requests on the same chain/prio of an\nunlocked classifier both run change() on the shared proto and both\ncan fail: the winner's tcf_chain_tp_delete_empty() attempt gives up\nbecause the loser's handle is still in the idr, and the loser's\nerror path drops only its own reference without a second reclamation\nattempt. The empty proto stays linked in the chain, holding the\nchain reference, a block reference and the classifier module\nreference until the chain or block is torn down.\n\nReclaim the proto on the error path of any failed request that holds\na proto reference. The reclamation is emptiness-gated:\ntcf_chain_tp_delete_empty() unlinks the proto only when\ndelete_empty() admits it is empty, so a live shared proto is never\nunlinked. A proto the request created is reclaimed unconditionally -\nit is the only owner, so marking it for deletion is safe even without\na delete_empty callback. Classifiers without one (the check marks the\nproto unconditionally) are rtnl-serialized, so the raced window this\nguard closes cannot arise for them.\n\nThis is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix\nteardown of an adopted proto on insert-race loss\"), which stopped the\nloser of the insert race from unlinking the winner's live proto but\nleft the empty-proto residual in place.\n\nConditions to recreate:\n- CONFIG_NET_CLS_FLOWER=y; veth pair\n- tc qdisc add dev veth0 ingress\n- two concurrent `tc filter add dev veth0 ingress protocol ip pref 1\n  flower skip_sw ... action drop` (both fail in fl_hw_replace_filter\n  after publishing their handle in the idr); repeat in a loop\n- an empty flower tp stays linked after both requests fail; visible\n  as a bare `filter protocol ip pref 1 flower chain 0` header in\n  `tc filter show` with no filter entries\n- CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"net/sched: cls_api: reclaim an empty proto on the error path","id":"CVE-2026-98811","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"net/mctp: publish the mctp_dev only after it is initialised","id":"CVE-2026-98812"},"packages":[],"prev":{"headline":"wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue()","id":"CVE-2026-98810"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's traffic control classifier allows local attackers to leak kernel memory and references, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-98811/"}