{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98591 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98591 is a vulnerability in Linux, published on 18 Oct 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-98591 and fix it if it is affected.\n\nWhat it is: CVE-2026-98591 is a vulnerability in Linux, published on 18 Oct 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-98591 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-98591/ (Markdown: https://insights.sbomify.com/CVE-2026-98591/index.md)","id":"CVE-2026-98591","markdown":"https://insights.sbomify.com/CVE-2026-98591/index.md","name":"CVE-2026-98591","record":{"aliases":["AZL-109223","BELL-CVE-2026-98591","DEBIAN-CVE-2026-98591","GHSA-4j29-hvp6-5v88","UBUNTU-CVE-2026-98591"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"An integer underflow in Linux kernel BPF bounds checking allows attackers to access invalid memory, potentially leading to code execution or privilege escalation.","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\nbpf: Fix bounds check for skb-backed dynptrs\n\nThe skb_pointer_if_linear() function checks whether a\nmemory region of length len starting at offset off into\nthe skb is in the linear area, and returns a pointer to\nthe region if so. The check currently subtracts between\nskb_headlen and offset of the check, and since skb_headlen\nis unsigned the subtraction can underflow. This causes the\nbounds check to spuriously pass and generate an arbitrary\npointer of the form *(skb-\u003edata + off).\n\nThe only user of this helper is currently skb-backed BPF\ndynptr code. Returning the wrong pointer leads to the\ndynptr erroneously being backed with invalid memory.\n\nEnsure the subtraction cannot underflow, and fail the check if\nit would. Use u64 arithmetic to also prevent overflow when\ncalculating (skb_headlen(skb) - off) since off is unsigned.","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":"bpf: Fix bounds check for skb-backed dynptrs","id":"CVE-2026-98591","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: spacemit: clear TX descriptor on fragment mapping failure","id":"CVE-2026-98592"},"packages":[],"prev":{"headline":"bpf: Fix bpf_sock context code generation","id":"CVE-2026-98590"},"products":["Linux"],"published":"2026-10-18","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":"An integer underflow in Linux kernel BPF bounds checking allows attackers to access invalid memory, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-98591/"}