Medium

Linux kernel nft_limit token-counter integer overflow

IdentifiersCVE-2024-26668CWE-190· Integer Overflow or Wraparound

CVE-2024-26668 is an integer-overflow flaw in the Linux kernel netfilter nft_limit implementation. nft_limit accepted rate-limit configurations whose extremely large requested rate caused its internal token counter to wrap around. The resulting wrapped value caused incorrect rate-limiting behavior. The fix rejects configurations that would overflow the internal counter.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker able to install or alter affected nftables limit rules could cause rate limiting to operate incorrectly, potentially bypassing intended traffic-throttling controls or producing unintended filtering behavior. The available information does not establish kernel code execution, privilege escalation, or a denial-of-service condition from this flaw alone.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed kernel is deployed, prohibit untrusted users and automation from creating or modifying nftables rules, and review nft_limit configurations for implausibly large byte-rate or packet-rate values. Enforce operational limits on configured rates to prevent values that can overflow nft_limit's internal token accounting.

Remediation

Patch, then assume compromise.

Update to a Linux kernel build containing the nft_limit integer-overflow validation fix, using the supported vendor kernel update for the affected distribution. Reboot after installing a non-live kernel update so that the corrected kernel is running.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

8 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity