netfilter: nf_tables: skip expired catchall elements on insert and delete
Summary
| CVE | CVE-2026-98484 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:16:59 UTC |
| Updated | 2026-10-21 13:21:31 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: skip expired catchall elements on insert and delete nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements. Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration. The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT. Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths. |
Risk And Classification
EPSS: 0.002000000 probability, percentile 0.093130000 (date 2026-10-21)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected aaa31047a6d25da0fa101da1ed544e1247949b40 5e20b39aa7844769a7a782484bc1a809ffbc513e git | Not specified |
| CNA | Linux | Linux | affected aaa31047a6d25da0fa101da1ed544e1247949b40 2f07da3881525f7cbfed1ced2796c71a201505b9 git | Not specified |
| CNA | Linux | Linux | affected aaa31047a6d25da0fa101da1ed544e1247949b40 12cf803edfffef96f6415f0b5dbc7ec88842ea0f git | Not specified |
| CNA | Linux | Linux | affected aaa31047a6d25da0fa101da1ed544e1247949b40 4fb8b1ccc475651e480e509de126bb9ce7f3cff9 git | Not specified |
| CNA | Linux | Linux | affected aaa31047a6d25da0fa101da1ed544e1247949b40 70194dc37670bd08e44b471389861cc01bd3a3c9 git | Not specified |
| CNA | Linux | Linux | affected 5.13 | Not specified |
| CNA | Linux | Linux | unaffected 5.13 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.112 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.55 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.9 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/70194dc37670bd08e44b471389861cc01bd3a3c9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4fb8b1ccc475651e480e509de126bb9ce7f3cff9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/12cf803edfffef96f6415f0b5dbc7ec88842ea0f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5e20b39aa7844769a7a782484bc1a809ffbc513e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2f07da3881525f7cbfed1ced2796c71a201505b9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.