CVE-2026-98588

bpf, sockmap: Reject max_entries > INT_MAX in sock_map_alloc

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Reject max_entries > INT_MAX in sock_map_alloc sock_map_alloc() only rejects max_entries == 0 and otherwise allows any u32 value. sock_map_free() then walks the sks[] array with a signed int iterator: int i; for (i = 0; i < stab->map.max_entries; i++) struct sock **psk = &stab->sks[i]; When a SOCKMAP is created with max_entries = 0xffffffff (UINT_MAX), the allocation of 32 GiB can succeed on large-memory hosts. During free the counter reaches 0x80000000, wraps to INT_MIN, is sign-extended by movslq and turned into a ~16 GiB negative offset from stab->sks, pointing far below the allocation. The faulting access is an xchg() write in sock_map_free(). Without KASAN, the same out-of-bounds write can fault on an unmapped vmalloc page or corrupt an unrelated allocation if that vmalloc address is populated. On a KASAN kernel with CONFIG_KASAN_VMALLOC=y, the shadow check for that address hits an unmapped shadow page and oopses first: BUG: unable to handle page fault for address: fffff521b59c5a00 RIP: 0010:kasan_check_range+0x107/0x190 Call Trace: sock_map_free+0x93/0x190 map_create+0x68d/0xb30 __sys_bpf+0x21e/0x2e70 Vmcore confirmed stab->map.max_entries == 0xffffffff, stab->sks == 0xffffc911ace2d000, and the faulting address sks + (s64)INT_MIN * 8 exactly at 0xffffc90dace2d000. The same buggy path is reached on the normal close()/bpf_map_free_deferred() path whenever such a map is destroyed. sock_map_alloc() used to bound its allocation size through bpf_map_charge_init(), but the bound was dropped when rlimit-based memory accounting was removed. Reject max_entries > INT_MAX at creation time so the signed iterator in sock_map_free() never sees a value that would overflow. Triggered by syzkaller and reproduced on both a 6.6-based KASAN kernel and the upstream v7.3-rc2 kernel.

Key facts

Published
18 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.211% likely to be exploited in the next 30 days, higher than 11.459% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding f4a73f49e256bd835368504462be3b57b03febff (affected)
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding c56191af3a578b9cc265fa3bd5fc0752c59c1781 (affected)
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding 909f761868fda329dc69130ef9eb5b5795bcdf00 (affected)
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding cc70972ddbf0e3398f2f32624d31db78594d50d8 (affected)
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding cea597519b9ca6d691c98d92460ead8ece2a07af (affected)
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding ba7d627dbc67d62df2fa66d7b41e743c3ace0ec8 (affected)
  • 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1 up to but excluding 814a81c842bd88f6bd8a4ce550d560df071a5d03 (affected)
LinuxLinux
  • Default status: affected
  • 5.11 (affected)
  • 0 up to but excluding 5.11 (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.55 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References