All reports
Medium

kernel: xsk: Use a 32-bit compare in xsk_map_gen_lookup

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98631

Probability of exploitation in the next 30 days: 0.21%

FIRST EPSS · 2026-11-19

Description

In the Linux kernel, the following vulnerability has been resolved: xsk: Use a 32-bit compare in xsk_map_gen_lookup xsk_map_gen_lookup() loads a u32 key and compares it with max_entries using BPF_JMP_IMM. BPF immediates are sign-extended to 64 bits, so a max_entries value of 0x80000000 or higher becomes a threshold larger than every zero-extended 32-bit key. An out-of-range index then skips the bounds check and the generated lookup reads past xsk_map[]. Compare with BPF_JMP32_IMM so the check stays in 32-bit unsigned range.

A flaw was found in the Linux kernel. A local attacker can cause a Denial of Service (DoS) or potentially expose sensitive memory by triggering an out-of-bounds read in the Berkeley Packet Filter (BPF) socket map implementation. This issue occurs because socket map lookups perform a 64-bit comparison on 32-bit keys, allowing out-of-range index values to bypass bounds checking when maps are configured with large entry limits.