{"cve":"CVE-2026-98588","nvd":{"published":"2026-10-18T16:17:11.393","modified":"2026-10-19T10:19:19.777","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf, sockmap: Reject max_entries > 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 < stab->map.max_entries; i++)\n\t\tstruct sock **psk = &stab->sks[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->sks, 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->map.max_entries == 0xffffffff, stab->sks ==\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 > 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.","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/814a81c842bd88f6bd8a4ce550d560df071a5d03","https://git.kernel.org/stable/c/909f761868fda329dc69130ef9eb5b5795bcdf00","https://git.kernel.org/stable/c/ba7d627dbc67d62df2fa66d7b41e743c3ace0ec8","https://git.kernel.org/stable/c/c56191af3a578b9cc265fa3bd5fc0752c59c1781","https://git.kernel.org/stable/c/cc70972ddbf0e3398f2f32624d31db78594d50d8"],"products":[],"source":"nvd","synced_at":"2026-10-19T23:00:53.604569364+00:00"},"epss":{"cve":"CVE-2026-98588","score":0.00211,"percentile":0.11302,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}