Kernel warning via stale nf_tables active state
Published Apr 17, 2024 · Updated May 23, 2026
State inconsistency in Linux kernel nf_tables allows local users to trigger a kernel warning during table or base-chain deletion. A hook-registration failure under memory pressure leaves the table marked active without registered hooks because its dormant flag is not restored. Reachability requires permission to manage nftables and the registration-failure condition; the published consequence is a warning when deletion attempts to unregister the absent hook.
Summary
What happened
State inconsistency in Linux kernel nf_tables allows local users to trigger a kernel warning during table or base-chain deletion. A hook-registration failure under memory pressure leaves the table marked active without registered hooks because its dormant flag is not restored. Reachability requires permission to manage nftables and the registration-failure condition; the published consequence is a warning when deletion attempts to unregister the absent hook.
The record
- CVE
- CVE-2024-26835
- Published
- Apr 17, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=179d9ba5559a756f4322583388b3213fe4e391b0 <0c9302a6da262e6ab6a6c1d30f04a6130ed97376
- Affected versionversion=179d9ba5559a756f4322583388b3213fe4e391b0 <664264a5c55bf97a9c571c557d477b75416199be
- Affected versionversion=179d9ba5559a756f4322583388b3213fe4e391b0 <6f2496366426cec18ba53f1c7f6c3ac307ca6a95
- Affected versionversion=179d9ba5559a756f4322583388b3213fe4e391b0 <bccebf64701735533c8db37773eeacc6566cc8ec
- Affected versionversion=179d9ba5559a756f4322583388b3213fe4e391b0 <f2135bbf14949687e96cabb13d8a91ae3deb9069
- Affected versionversion=5.10.202 <5.10.211
- Affected versionversion=5.13
- Affected versionversion=5.4.262 <5.4.270
- Affected versionversion=bf8083bbf8fa202e6e5316bbd99759ab82bfe7a3 <a6411f3c48f991c19aaf9a24fce36865fbba28d7
- Affected versionversion=d9c4da8cb74e8ee6e58a064a3573aa37acf6c935 <31ea574aeca1aa488e18716459bde057217637af
- Affected versionversion=e10f661adc556c4969c70ddaddf238bffdaf1e87 <ae4360cbd385f0d7a8a86d5723e50448cc6318f3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo