{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98588 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98588 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-98588 and fix it if it is affected.\n\nWhat it is: CVE-2026-98588 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-98588 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-98588/ (Markdown: https://insights.sbomify.com/CVE-2026-98588/index.md)","id":"CVE-2026-98588","markdown":"https://insights.sbomify.com/CVE-2026-98588/index.md","name":"CVE-2026-98588","record":{"aliases":["AZL-108951","BELL-CVE-2026-98588","DEBIAN-CVE-2026-98588","GHSA-v3gv-6qr6-4mh5","UBUNTU-CVE-2026-98588"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"An integer overflow in Linux kernel sockmap allocation allows local attackers to trigger out-of-bounds writes, causing crashes or potential code execution.","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, sockmap: Reject max_entries \u003e INT_MAX in sock_map_alloc\n\nsock_map_alloc() only rejects max_entries == 0 and otherwise allows any\nu32 value.  sock_map_free() then walks the sks[] array with a signed int\niterator:\n\n\tint i;\n\tfor (i = 0; i \u003c stab-\u003emap.max_entries; i++)\n\t\tstruct sock **psk = \u0026stab-\u003esks[i];\n\nWhen a SOCKMAP is created with max_entries = 0xffffffff (UINT_MAX), the\nallocation of 32 GiB can succeed on large-memory hosts.  During free the\ncounter reaches 0x80000000, wraps to INT_MIN, is sign-extended by movslq\nand turned into a ~16 GiB negative offset from stab-\u003esks, pointing far\nbelow the allocation.\n\nThe faulting access is an xchg() write in sock_map_free().  Without\nKASAN, the same out-of-bounds write can fault on an unmapped vmalloc page\nor corrupt an unrelated allocation if that vmalloc address is populated.\nOn a KASAN kernel with CONFIG_KASAN_VMALLOC=y, the shadow check for that\naddress hits an unmapped shadow page and oopses first:\n\n  BUG: unable to handle page fault for address: fffff521b59c5a00\n  RIP: 0010:kasan_check_range+0x107/0x190\n  Call Trace:\n   sock_map_free+0x93/0x190\n   map_create+0x68d/0xb30\n   __sys_bpf+0x21e/0x2e70\n\nVmcore confirmed stab-\u003emap.max_entries == 0xffffffff, stab-\u003esks ==\n0xffffc911ace2d000, and the faulting address sks + (s64)INT_MIN * 8\nexactly at 0xffffc90dace2d000.  The same buggy path is reached on the\nnormal close()/bpf_map_free_deferred() path whenever such a map is\ndestroyed.\n\nsock_map_alloc() used to bound its allocation size through\nbpf_map_charge_init(), but the bound was dropped when rlimit-based memory\naccounting was removed.  Reject max_entries \u003e INT_MAX at creation time so\nthe signed iterator in sock_map_free() never sees a value that would\noverflow.\n\nTriggered by syzkaller and reproduced on both a 6.6-based KASAN kernel\nand the upstream v7.3-rc2 kernel.","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, sockmap: Reject max_entries \u003e INT_MAX in sock_map_alloc","id":"CVE-2026-98588","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"bpf: Reject pkt arguments in mutating subprogs","id":"CVE-2026-98589"},"packages":[],"prev":{"headline":"firewire: cdev: fix back-transition for iso_resource_auto client resource","id":"CVE-2026-98587"},"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 overflow in Linux kernel sockmap allocation allows local attackers to trigger out-of-bounds writes, causing crashes or potential code execution.","url":"https://insights.sbomify.com/CVE-2026-98588/"}