CVE-2026-89579
bpf: Harden bloom filter sizing and indexing on 32-bit kernels
Reported by linux · Published September 11, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: Harden bloom filter sizing and indexing on 32-bit kernels bloom_map_alloc() has two 32-bit-specific problems when the computed bitmap reaches the U32_MAX fallback case. First, BITS_TO_BYTES(U32_MAX) is evaluated with 32-bit arithmetic. The addition performed by DIV_ROUND_UP wraps, so the map allocates only the fixed-size bloom filter object while keeping bitset_mask == U32_MAX. Subsequent updates can then write past the allocated object. Second, fixing only the allocation size is not sufficient. The bloom hash is a u32, but set_bit() takes a signed long bit number and x86 test_bit() eventually feeds the index to variable_test_bit(long, ...). On 32-bit kernels, hashes in [0x80000000, U32_MAX] therefore become negative bit offsets. x86 bt/bts with a memory operand interpret those offsets relative to the supplied base, so a map with bitset_mask == U32_MAX can read or write before bloom->bitset even after allocating the full 512 MiB bitmap. Keep the U32_MAX fallback, but split each hash into a word pointer and an in-word bit number before calling test_bit() or set_bit(). The bitops argument is then always in [0, BITS_PER_LONG - 1], while BIT_WORD(h) still selects the intended word in the full bitmap. Compute the bitset size from (u64)bitset_mask + 1 before passing the final size to bpf_map_area_alloc(). This fixes the original under-allocation and keeps the allocated storage consistent with the addressable bitset. Exploitation note: local privilege escalation is possible on a 32-bit x86 kernel using the under-allocation bug from a binary with CAP_BPF.
EPSS 0.17% · 6.0th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-tools-devel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel-livepatch-6.18.51-120.162 | Amazon Linux | 1:1.0-0.amzn2023 |
| kernel6.18-tools-devel | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel-modules-extra | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.12-tools-devel | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel6.12-devel | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel6.12-modules-extra | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel-devel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel-livepatch-6.12.110-135.201 | Amazon Linux | 1:1.0-0.amzn2023 |
| bpftool6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel-tools | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel-headers | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
15 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 9330986c03006ab1d33d243b7cfe598a7a3c1baa, 9330986c03006ab1d33d243b7cfe598a7a3c1baa, 9330986c03006ab1d33d243b7cfe598a7a3c1baa |
| Linux | Linux | 5.16, 0, 6.1.188 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel-livepatch-6.12.110-135.201 | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
…and 18 more
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (9 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-89579
vulnetix vdb fixes CVE-2026-89579
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89579/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart