CVE-2024-26668: netfilter: nft_limit: reject configurations that cause integer overflow
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_limit: reject configurations that cause integer overflow
Reject bogus configs where internal token counter wraps around.
This only occurs with very very large requests, such as 17gbyte/s.
Its better to reject this rather than having incorrect ratelimit.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects nftables rate limiting. Extremely large rate-limit configurations can make an internal counter wrap, causing incorrect rate-limit behavior instead of being rejected. The available sources do not show code execution, privilege escalation, data theft, or active exploitation.
Executive priority
Treat as a routine kernel maintenance item unless critical systems rely heavily on nftables rate limiting. Current evidence does not support emergency response, but affected kernels should be updated through normal patch channels.
Technical view
CVE-2024-26668 is an integer overflow condition in Linux netfilter nft_limit. Bogus configurations with very large rates can wrap the internal token counter. The fix rejects configurations that would overflow, preserving correct ratelimit behavior.
Likely exposure
Exposure is most relevant to Linux systems using nftables/netfilter rate limiting on affected kernel builds. The source lists Linux kernel affected versions and stable commit references, but distribution-specific package status is not provided.
Exploitation context
CISA KEV status is false in the provided bundle. The description frames this as a configuration-triggered correctness issue requiring very large requested rates, such as 17 GB/s. No public exploitation evidence is provided.
Researcher notes
The public bundle lacks CVSS, CWE, exploit detail, and distribution mapping. Analysis should stay limited to nft_limit integer overflow and incorrect ratelimit behavior. Validate against exact kernel trees or distribution backports before declaring exposure.
Mitigation direction
Apply vendor Linux kernel updates that include the referenced stable fixes.
Check distribution advisories for CVE-2024-26668 package status.
Review nftables rate-limit configurations for unrealistic very large rates.
Prioritize internet-facing gateways and multi-tenant Linux hosts using nftables.
Validation and detection
Inventory Linux kernel versions across affected hosts.
Confirm installed kernel changelogs reference CVE-2024-26668 or the stable commits.
Identify systems using nftables limit expressions.
After patching, verify vulnerability scanners no longer report this CVE.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
description · low confidence lookup
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.