CVE-2026-52921: netfilter: ipset: stop hash:* range iteration at end
In the Linux kernel, the following vulnerability has been resolved:
netfilter: ipset: stop hash: range iteration at end
The following hash set variants:
hash:ip,mark hash:ip,port hash:ip,port,ip hash:ip,port,net
iterate IPv4 ranges with a 32-bit iterator.
The iterator must stop once the last address in the requested range has been processed. Advancing it once more can move the traversal state past the end of the request, so a later retry may continue from an unintended position.
Handle the iterator increment explicitly at the end of the loop and stop once the upper bound has been processed. This keeps the existing retry behaviour intact for valid ranges while preventing traversal from continuing past the original boundary.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1 - Compensating control
Update/upgrade the Linux kernel to a version where the ipset netfilter fix is applied: stop hash:* range iteration once the last address in the requested range (upper bound) has been processed, preventing traversal past the original boundary while keeping existing retry behavior intact for valid ranges.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-52921?
CVE-2026-52921 has a risk score of 13, indicating a high level of severity.
How do I fix CVE-2026-52921?
To fix CVE-2026-52921, update your Linux kernel to the latest version that contains the patch for this vulnerability.
What systems are affected by CVE-2026-52921?
CVE-2026-52921 affects systems utilizing the Linux netfilter ipset module, specifically with hash set variants like hash:ip and hash:ip,port.
What does CVE-2026-52921 affect in the Linux kernel?
CVE-2026-52921 affects the iteration process of IPv4 ranges in certain hash set variants within the netfilter ipset implementation.
Is CVE-2026-52921 exploitable?
CVE-2026-52921 is considered exploitable due to its potential to allow incorrect handling of the end of hash iteration.