Skip to main content
VulnerabilityPublished

CVE-2026-98588: Linux kernel · bpf, sockmap: Reject max_entries > INT_MAX in sock_map_alloc

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f4a73f49e256bd835368504462be3b57b03febff : patch Linux kernel soon.

Data as of 26 Oct 2026, 12:55 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f4a73f49e256bd835368504462be3b57b03febff, cea597519b9ca6d691c98d92460ead8ece2a07af, cc70972ddbf0e3398f2f32624d31db78594d50d8 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1, < f4a73f49e256bd835368504462be3b57b03febff
Fixed in
  • f4a73f49e256bd835368504462be3b57b03febff
LinuxLinuxAffected
  • ≥ 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1, < cea597519b9ca6d691c98d92460ead8ece2a07af
Fixed in
  • cea597519b9ca6d691c98d92460ead8ece2a07af
LinuxLinuxAffected
  • ≥ 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1, < cc70972ddbf0e3398f2f32624d31db78594d50d8
Fixed in
  • cc70972ddbf0e3398f2f32624d31db78594d50d8
LinuxLinuxAffected
  • ≥ 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1, < c56191af3a578b9cc265fa3bd5fc0752c59c1781
Fixed in
  • c56191af3a578b9cc265fa3bd5fc0752c59c1781
LinuxLinuxAffected
  • ≥ 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1, < ba7d627dbc67d62df2fa66d7b41e743c3ace0ec8
Fixed in
  • ba7d627dbc67d62df2fa66d7b41e743c3ace0ec8
LinuxLinuxAffected
  • ≥ 0d2c4f9640501ff57ba0be1f5644a02c29a02fa1, < 909f761868fda329dc69130ef9eb5b5795bcdf00
Fixed in
  • 909f761868fda329dc69130ef9eb5b5795bcdf00

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and has been applied in multiple Linux kernel commits. The vulnerability is mitigated by rejecting max_entries values greater than INT_MAX during sockmap creation, preventing the integer overflow in sock_map_free(). Users should update to a Linux kernel version that includes the fix identified by the commits (e.g., f4a73f49e256bd835368504462be3b57b03febff and others).

Description

A vulnerability in the Linux kernel's BPF sockmap implementation allows creation of sockmaps with max_entries greater than INT_MAX, leading to an integer overflow in sock_map_free(). This causes out-of-bounds memory writes during map destruction, potentially resulting in memory corruption or kernel crashes. The issue arises because sock_map_alloc() did not properly reject large max_entries values, allowing a signed integer iterator in sock_map_free() to overflow. The flaw has been fixed by rejecting max_entries values greater than INT_MAX at creation time.

References

Community reviews

Loading reviews…