{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90109 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90109 is a 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-90109 and fix it if it is affected.\n\nWhat it is: CVE-2026-90109 is a 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-90109 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-90109/ (Markdown: https://insights.sbomify.com/CVE-2026-90109/index.md)","id":"CVE-2026-90109","markdown":"https://insights.sbomify.com/CVE-2026-90109/index.md","name":"CVE-2026-90109","record":{"aliases":["AZL-102656","BELL-CVE-2026-90109","DEBIAN-CVE-2026-90109","GHSA-6qjr-4f2g-wppr","UBUNTU-CVE-2026-90109"],"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":"high_privilege","summary":"A 32-bit integer overflow in Linux kernel network schedulers allows root users to cause unbounded queue growth and system OOM.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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: fix 32-bit backlog wrap in gred, bfifo and plug enqueue\n\ngred_enqueue(), bfifo_enqueue() and plug_enqueue() admit a packet when the\ncurrent backlog plus the packet length fits within the queue limit:\n\n  sch-\u003eqstats.backlog + qdisc_pkt_len(skb) \u003c= sch-\u003elimit (gred default VQ)\n  gred_backlog+qdisc_pkt_len(skb) \u003c= q-\u003elimit  (gred configured VQ)\n  sch-\u003eqstats.backlog + qdisc_pkt_len(skb) \u003c= sch-\u003elimit (bfifo)\n  sch-\u003eqstats.backlog + skb-\u003elen \u003c= q-\u003elimit             (plug)\n\nsch-\u003eqstats.backlog and q-\u003ebacklog are u32, and qdisc_pkt_len()/skb-\u003elen\nare unsigned int, so all sums are computed in 32 bits and wrap at 2^32.\nOnce the true backlog exceeds 4 GiB the wrapped sum becomes small and\nadmission keeps succeeding, so the queue grows without bound and the kernel\ncan be driven to OOM.\n\nPromote the sums to u64 so admission stops once the true backlog exceeds\nthe limit.  The limit is u32, so the bounded queue stays below 2^32 and\nthe stored u32 backlog never wraps.\n\nThe bug can only be reproduced as root (albeit with ridiculous setup):\n attach a gred (or bfifo/plug) qdisc with a limit near 4 GiB,\n leaving the default VQ unconfigured (for gred), and drive \u003e4 GiB of\n queued traffic (e.g. via a size table / stab to inflate qdisc_pkt_len,\n or sustained high-rate traffic). The u32 backlog+len sum wraps at 2^32,\n admission keeps succeeding, and the queue grows unboundedly to OOM.","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: fix 32-bit backlog wrap in gred, bfifo and plug enqueue","id":"CVE-2026-90109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"inetpeer: randomize RB-tree node comparison using SipHash","id":"CVE-2026-90110"},"packages":[],"prev":{"headline":"net/smc: free stashed qentry before overwrite in REQ_ADD_LINK to ADD_LINK transition","id":"CVE-2026-90108"},"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-21","vendors":["Linux"]},"summary":"A 32-bit integer overflow in Linux kernel network schedulers allows root users to cause unbounded queue growth and system OOM.","url":"https://insights.sbomify.com/CVE-2026-90109/"}