Linux
netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() nft_map_catchall_activate() has an inverted element activity check compared to its non-catchall counterpart nft_mapelem_activate() and compared to what is logically required. nft_map_catchall_activate() is called from the abort path to re-activate catchall map elements that were deactivated during a failed transaction. It should skip elements that are already active (they don't need re-activation) and process elements that are inactive (they need to be restored). Instead, the current code does the opposite: it skips inactive elements and processes active ones. Compare the non-catchall activate callback, which is correct: nft_mapelem_activate(): if (nft_set_elem_active(ext, iter->genmask)) return 0; /* skip active, process inactive */ With the buggy catchall version: nft_map_catchall_activate(): if (!nft_set_elem_active(ext, genmask)) continue; /* skip inactive, process active */ The consequence is that when a DELSET operation is aborted, nft_setelem_data_activate() is never called for the catchall element. For NFT_GOTO verdict elements, this means nft_data_hold() is never called to restore the chain->use reference count. Each abort cycle permanently decrements chain->use. Once chain->use reaches zero, DELCHAIN succeeds and frees the chain while catchall verdict elements still reference it, resulting in a use-after-free. This is exploitable for local privilege escalation from an unprivileged user via user namespaces + nftables on distributions that enable CONFIG_USER_NS and CONFIG_NF_TABLES. Fix by removing the negation so the check matches nft_mapelem_activate(): skip active elements, process inactive ones.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 25aa2ad37c2162be1c0bc4fe6397f7e4c13f00f8, < 8c760ba4e36c750379d13569f23f5a6e185333f5
- >= d60be2da67d172aecf866302c91ea11533eca4d9, < b9b6573421de51829f7ec1cce76d85f5f6fbbd7f
- >= 628bd3e49cba1c066228e23d71a852c23e26da73, < 42c574c1504aa089a0a142e4c13859327570473d
- >= 628bd3e49cba1c066228e23d71a852c23e26da73, < 1444ff890b4653add12f734ffeffc173d42862dd
- >= 628bd3e49cba1c066228e23d71a852c23e26da73, < 8b68a45f9722f2babe9e7bad00aa74638addf081
- >= 628bd3e49cba1c066228e23d71a852c23e26da73, < f41c5d151078c5348271ffaf8e7410d96f2d82f8
- bc9f791d2593f17e39f87c6e2b3a36549a3705b1
- 3c7ec098e3b588434a8b07ea9b5b36f04cef1f50
- a136b7942ad2a50de708f76ea299ccb45ac7a7f9
- dc7cdf8cbcbf8b13de1df93f356ec04cdeef5c41
- >= 5.15.121, < 5.15.200
- >= 6.1.36, < 6.1.163
- >= 4.19.316, < 4.20
- >= 5.4.262, < 5.5
- >= 5.10.188, < 5.11
- >= 6.3.10, < 6.4
Fixed in 8c760ba4e36c750379d13569f23f5a6e185333f5, b9b6573421de51829f7ec1cce76d85f5f6fbbd7f, 42c574c1504aa089a0a142e4c13859327570473d, 1444ff890b4653add12f734ffeffc173d42862dd, 8b68a45f9722f2babe9e7bad00aa74638addf081, f41c5d151078c5348271ffaf8e7410d96f2d82f8, 5.15.200, 6.1.163, 4.20, 5.5, 5.11, 6.4
- 6.4
Fixed in 0, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 6.19
Mitigation
Upgrade Linux to 8c760ba4e36c750379d13569f23f5a6e185333f5 or b9b6573421de51829f7ec1cce76d85f5f6fbbd7f or 42c574c1504aa089a0a142e4c13859327570473d or 1444ff890b4653add12f734ffeffc173d42862dd or 8b68a45f9722f2babe9e7bad00aa74638addf081 or f41c5d151078c5348271ffaf8e7410d96f2d82f8 or 5.15.200 or 6.1.163 or 4.20 or 5.5 or 5.11 or 6.4 or later.
Upgrade Linux to 0 or 5.15.200 or 6.1.163 or 6.6.124 or 6.12.70 or 6.18.10 or 6.19 or later.
Timeline
Days relative to CVE publicationFirst public PoC 116 days after publication; not in CISA KEV. First PoC: criann/check-cve-2026-23111 (created 9 Jun 2026, found by us: backfilled).
PoC repositories
Found on GitHub.10 PoCs · 1 informational · 2 suspicious or fake
PoCs 10
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| criann/check-cve-2026-23111 | 9 Jun 2026 +116 d | backfilled | 0 | Scanner
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
| 0xBlackash/CVE-2026-23111 | 9 Jun 2026 +116 d | backfilled | 5 | PoC via PoC Index |
| 0xredash/CVE-2026-23111 | 9 Jun 2026 +116 d | backfilled | 5 | PoC via PoC Index |
| ashrafzaryouh/CVE-2026-23111 | 9 Jun 2026 +116 d | backfilled | 5 | PoC via PoC Index |
| seguridadentrerios/CVE-2026-23111 | 10 Jun 2026 +117 d | backfilled | 0 | PoC via PoC Index |
| ishankaru/CVE-2026-23111-nftables-lab | 11 Jun 2026 +118 d | backfilled | 2 | PoC |
| Baba01hacker666/CVE-2026-23111 | 25 Jun 2026 +132 d | backfilled | 7 | PoC |
| letsr00t/nft-catchall-uaf | 28 Jun 2026 +135 d | backfilled | 1 | PoC |
| imeiplus/CVE-2026-23111-PoC | 20 Sep 2026 +219 d | backfilled | 0 | PoC |
| kinokopio/CVE-2026-23111 | 19 Oct 2026 +248 d | 14 Nov 2026 | 6 | PoC |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| HORKimhab/CVE-2026-23111 | 9 Jun 2026 +115 d | 0 | Informational · write-up |
Suspicious or fake 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| bakano98/cve-2026-23111-poc | 1 Jul 2026 +138 d | 1 | Fake |
| Knz-source/CVE-2026-23111-POC-noddlenpottato | 12 Aug 2026 +180 d | 10 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.