{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80993 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80993 is a vulnerability in Linux, published on 11 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-80993 and fix it if it is affected.\n\nWhat it is: CVE-2026-80993 is a vulnerability in Linux, published on 11 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-80993 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-80993/ (Markdown: https://insights.sbomify.com/CVE-2026-80993/index.md)","id":"CVE-2026-80993","markdown":"https://insights.sbomify.com/CVE-2026-80993/index.md","name":"CVE-2026-80993","record":{"aliases":["BELL-CVE-2026-80993","DEBIAN-CVE-2026-80993","GHSA-v77c-jw3g-56gh","UBUNTU-CVE-2026-80993"],"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":"none","summary":"A missing error check in the Linux kernel's phylink subsystem allows a local attacker to trigger a kernel panic via a null pointer dereference.","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: phylink: correctly validate returned PCS in phylink_inband_caps\n\nIn phylink_inband_caps(), the PCS returned by mac_select_pcs is only\nchecked if NULL but mac_select_pcs can also return an error pointer.\n\nThis can cause a kernel panic as phylink_pcs_inband_caps() only checks\nif passed PCS is not NULL and directly dereference ops from the phylink_pcs\nstruct.\n\nUse the IS_ERR_OR_NULL macro to address both case where the returned\nPCS can be NULL or an error pointer and prevent a kernel panic.","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: phylink: correctly validate returned PCS in phylink_inband_caps","id":"CVE-2026-80993","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"net: openvswitch: fix flow mask use-after-free on flow deletion","id":"CVE-2026-80994"},"packages":[],"prev":{"headline":"net: ravb: avoid dereferencing an invalid PTP clock","id":"CVE-2026-80992"},"products":["Linux"],"published":"2026-09-11","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 missing error check in the Linux kernel's phylink subsystem allows a local attacker to trigger a kernel panic via a null pointer dereference.","url":"https://insights.sbomify.com/CVE-2026-80993/"}