{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90058 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90058 is a denial of service vulnerability in Linux, published on 17 Sep 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-90058 and fix it if it is affected.\n\nWhat it is: CVE-2026-90058 is a denial of service vulnerability in Linux, published on 17 Sep 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-90058 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-90058/ (Markdown: https://insights.sbomify.com/CVE-2026-90058/index.md)","id":"CVE-2026-90058","markdown":"https://insights.sbomify.com/CVE-2026-90058/index.md","name":"CVE-2026-90058","record":{"aliases":["AZL-102933","BELL-CVE-2026-90058","DEBIAN-CVE-2026-90058","GHSA-59qr-qww5-6w4f","UBUNTU-CVE-2026-90058"],"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 crafted size table in Linux kernel qdisc schedulers can cause a soft lockup, allowing local attackers to crash the system.","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: bound qdisc_pkt_len to prevent qdisc soft lockup\n\nqdisc_get_stab() accepts a user-supplied size table, and\n__qdisc_calculate_pkt_len() amplifies qdisc_pkt_len() through the\noverhead, the size-table data (u16), and size_log (up to\nSTAB_SIZE_LOG_MAX). A crafted stab can therefore set qdisc_pkt_len()\nto ~1 GiB for an ordinary skb. Per-flow deficit schedulers such as\nDRR and ETS replenish one quantum per loop iteration; with a tiny\nquantum (1) they spin billions of times under the qdisc lock,\nproducing a soft lockup / RCU stall as illustrated by vega@nebusec.ai.\n\nCap the final qdisc_pkt_len() to QDISC_PKT_LEN_MAX so the size-table\namplification cannot drive deficit schedulers into an unbounded loop.\nA legitimate size table (e.g. qfq's overhead 999999999, which is\nhandled by dropping) is still accepted.\n\nIntroduce cap QDISC_PKT_LEN_MAX (1 \u003c\u003c 20) = 1 MiB which is well above\nany legitimate single-skb wire length: the largest current skb-\u003elen\nis GSO_MAX_SIZE (524280), and an ATM-style size table (53/48 cell tax)\namplifies that to ~578 KB, both comfortably below 1 MiB. At the same\ntime, 1 MiB bounds the deficit refill loop to ~1M iterations per\npacket with quantum=1, which completes in a few milliseconds well\nunder the demonstrated softlockup threshold (~10^9 iterations).\n\nConditions to recreate the bug:\n- CONFIG_NET_SCHED=y, CONFIG_NET_SCH_DRR=y (or CONFIG_NET_SCH_ETS=y).\n- Attach a DRR (or ETS) root qdisc with a crafted TCA_STAB that\n  amplifies qdisc_pkt_len to ~1 GiB (e.g. size_log=15, data=[32768]).\n- Add a class with a tiny quantum of 1 and send one small packet; the\n  deficit loop spins billions of times under the qdisc lock and trips\n  the softlockup detector (panic with kernel.softlockup_panic=1).\n- Reachable as root or from an unprivileged user in a fresh user+net\n  namespace (unshare -Urn) with namespace-local CAP_NET_ADMIN.","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: bound qdisc_pkt_len to prevent qdisc soft lockup","id":"CVE-2026-90058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net: stmmac: restore NET_IP_ALIGN in the RX DMA offset","id":"CVE-2026-90059"},"packages":[],"prev":{"headline":"slip: remove slip_hangup() to fix use-after-free in slip_receive_buf()","id":"CVE-2026-90057"},"products":["Linux"],"published":"2026-09-17","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 crafted size table in Linux kernel qdisc schedulers can cause a soft lockup, allowing local attackers to crash the system.","url":"https://insights.sbomify.com/CVE-2026-90058/"}