{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98380 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98380 is a vulnerability in Linux, published on 9 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-98380 and fix it if it is affected.\n\nWhat it is: CVE-2026-98380 is a vulnerability in Linux, published on 9 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-98380 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-98380/ (Markdown: https://insights.sbomify.com/CVE-2026-98380/index.md)","id":"CVE-2026-98380","markdown":"https://insights.sbomify.com/CVE-2026-98380/index.md","name":"CVE-2026-98380","record":{"aliases":["AZL-106908","BELL-CVE-2026-98380","DEBIAN-CVE-2026-98380","GHSA-j546-37mc-3c35","UBUNTU-CVE-2026-98380"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's traffic control subsystem allows a local attacker to trigger a null pointer dereference, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: reject IDR error pointers when deleting actions\n\ntcf_action_delete() drops the reference held by its lookup before calling\ntcf_idr_delete_index() with the saved action index.  An unlocked\nclassifier can remove that action and reserve the same IDR slot with\nERR_PTR(-EBUSY) in between.\n\ntcf_idr_delete_index() only checks the lookup result for NULL.  It\ntherefore treats the reservation as a tc_action and dereferences\ntcfa_bindcnt.  A hardware execution breakpoint was used to schedule the\ninterleaving without changing the kernel source.  KASAN reported this\ndecoded trace:\n\n  BUG: KASAN: null-ptr-deref in tca_action_gd+0x5b9/0x1010\n  Read of size 4 at addr 0000000000000010 by task poc/150\n  Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002\n  RIP: tca_action_gd+0x5c0/0x1010:\n    arch_atomic_read at arch/x86/include/asm/atomic.h:23\n    raw_atomic_read at include/linux/atomic/atomic-arch-fallback.h:457\n    atomic_read at include/linux/atomic/atomic-instrumented.h:33\n    tcf_idr_delete_index at net/sched/act_api.c:766\n    tcf_action_delete at net/sched/act_api.c:1859\n    tcf_del_notify at net/sched/act_api.c:2014\n    tca_action_gd at net/sched/act_api.c:2064\n  R13: 0000000000000010 R15: fffffffffffffff0\n  Kernel panic - not syncing: Fatal exception\n\nR15 contains ERR_PTR(-EBUSY), and adding the tcfa_bindcnt offset produces\nthe address in R13.  With the guard applied, the same reproducer returned\n-ENOENT without a KASAN report or panic.  Treat error pointers as absent\nand return -ENOENT.","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: reject IDR error pointers when deleting actions","id":"CVE-2026-98380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"veth: manage XDP program pointers during channel resize","id":"CVE-2026-98381"},"packages":[],"prev":{"headline":"netfilter: ip6t_rpfilter: reject routes without inet6_dev","id":"CVE-2026-98379"},"products":["Linux"],"published":"2026-10-09","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-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's traffic control subsystem allows a local attacker to trigger a null pointer dereference, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-98380/"}