{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90076 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90076 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-90076 and fix it if it is affected.\n\nWhat it is: CVE-2026-90076 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-90076 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-90076/ (Markdown: https://insights.sbomify.com/CVE-2026-90076/index.md)","id":"CVE-2026-90076","markdown":"https://insights.sbomify.com/CVE-2026-90076/index.md","name":"CVE-2026-90076","record":{"aliases":["AZL-102791","BELL-CVE-2026-90076","DEBIAN-CVE-2026-90076","GHSA-6j38-2pg6-m9mv","UBUNTU-CVE-2026-90076"],"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 local attacker with CAP_NET_ADMIN can cause a kernel soft lockup by configuring a network device with an excessively large MTU, leading to an integer overflow in the fq scheduler.","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: fq: add overflow bounds to quantum and initial quantum\n\nfq_init() computes quantum = 2 * psched_mtu() and initial_quantum = 10 *\npsched_mtu() with no overflow check. A device with a huge MTU (e.g. dummy\nwith max_mtu == 0 accepting MTU 2147483634) makes psched_mtu() return\n0x80000000; the 2 * and 10 * multiplications wrap to 0 in 32-bit\narithmetic, so q-\u003equantum == 0. Then in fq_dequeue() the credit-refill\nloop adds 0 to f-\u003ecredit (which stays \u003c= 0) and goto begin loops\nforever under the qdisc lock, creating a soft lockup.\n\nClamp psched_mtu() to [1, 1 \u003c\u003c 20] before multiplying so the product\ncannot wrap, then cap the result at 1 \u003c\u003c 20, matching the bound already\nenforced on TCA_FQ_QUANTUM in fq_change().\n\nConditions to recreate the bug: a device whose MTU (plus\nhard_header_len) is large enough that 2 * psched_mtu() wraps (e.g. a\ndummy device with max_mtu == 0 accepting MTU 2147483634). Requires\nCAP_NET_ADMIN in a user namespace.","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: fq: add overflow bounds to quantum and initial quantum","id":"CVE-2026-90076","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":"net: fix a resource leak in copy_net_ns() error handling path","id":"CVE-2026-90077"},"packages":[],"prev":{"headline":"net/sched: fq_codel: clamp default quantum and mtu","id":"CVE-2026-90075"},"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 local attacker with CAP_NET_ADMIN can cause a kernel soft lockup by configuring a network device with an excessively large MTU, leading to an integer overflow in the fq scheduler.","url":"https://insights.sbomify.com/CVE-2026-90076/"}