{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90083 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90083 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-90083 and fix it if it is affected.\n\nWhat it is: CVE-2026-90083 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-90083 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-90083/ (Markdown: https://insights.sbomify.com/CVE-2026-90083/index.md)","id":"CVE-2026-90083","markdown":"https://insights.sbomify.com/CVE-2026-90083/index.md","name":"CVE-2026-90083","record":{"aliases":["AZL-102546","BELL-CVE-2026-90083","DEBIAN-CVE-2026-90083","GHSA-28qx-7jq4-9v6v","UBUNTU-CVE-2026-90083"],"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 high privileges can trigger a kernel panic in the Linux kernel's IFE traffic control action by redirecting non-Ethernet frames.","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: act_ife: Only operate on Ethernet frames\n\nact_ife encapsulates/decapsulates the original Ethernet header and uses\nskb-\u003edev-\u003ehard_header_len as the length of that header. That is only\ncorrect for Ethernet devices: on a device where hard_header_len does not\nmatch the L2 header that was actually pulled (PPP reports PPP_HDRLEN\nwhile nothing is stripped on ingress), the ingress skb_push()/skb_pull()\nuse the wrong length and can hit skb_under_panic when headroom is tight.\n\nIFE is Ethernet-only by design - it builds an outer ethhdr, rewrites\nh_source/h_dest/h_proto, and calls eth_type_trans() on decode - so\ninstead of trying to make the offsets work for arbitrary link types,\nsimply drop packets that do not carry an Ethernet header.\n\nChecking skb-\u003edev-\u003etype alone is not enough. We have to cater for a\ncorner case where mirred can redirect an skb from a non-Ethernet device\nto an Ethernet one, and skb-\u003edev then says nothing about the framing the\nskb actually has: an skb redirected from ppp0 reaches the target's ingress\nhook with mac_len 0 and no Ethernet header at all. So at ingress also\nrequire mac_len to be ETH_HLEN. On egress mac_len is not maintained, so\nthe device type is all we have; a bogus redirect there yields a malformed\nframe rather than an out-of-bounds push, and it would be malformed with or\nwithout IFE.\n\nThat corner case is not theoretical - redirecting from ppp0 into a veth\nthat has an ife encode action on its ingress hook panics without this\npatch:\n\n  skbuff: skb_under_panic: len:98 put:14 head:ffff88800e410000\n          data:ffff88800e40fff5 tail:0x57 end:0x640 dev:veth3\n  kernel BUG at net/core/skbuff.c:214!\n  Call Trace:\n   skb_push (net/core/skbuff.c:224 net/core/skbuff.c:2657)\n   tcf_ife_act (net/sched/act_ife.c:829 net/sched/act_ife.c:874)\n   tc_run (net/core/dev.c:4463)\n   netif_receive_skb (net/core/dev.c:6463 net/core/dev.c:6522)\n   tcf_mirred_to_dev (net/sched/act_mirred.c:248 net/sched/act_mirred.c:328)\n   tcf_mirred_act (net/sched/act_mirred.c:489)\n   tc_run (net/core/dev.c:4463)\n   process_backlog (net/core/dev.c:6728)\n\nWith Ethernet framing guaranteed, use ETH_HLEN instead of\nhard_header_len.","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: act_ife: Only operate on Ethernet frames","id":"CVE-2026-90083","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":"octeontx2-vf: fix workqueue and netdev race in probe/remove","id":"CVE-2026-90084"},"packages":[],"prev":{"headline":"net: mana: Cap MSI-X vectors to the device MSI-X table size","id":"CVE-2026-90082"},"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 high privileges can trigger a kernel panic in the Linux kernel's IFE traffic control action by redirecting non-Ethernet frames.","url":"https://insights.sbomify.com/CVE-2026-90083/"}