GHSA-jh9m-9mr6-3ghc · 深刻度： high — In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix...
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.
総合評価: CVE-2026-23111 は中リスク（40.6/100）。CVSS 深刻度は高。悪用される可能性が高い（EPSS 0.34%、26 パーセンタイル） 推奨対応: 影響資産を整理し、修補計画に組み込んでください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-06-30 | 0.19% | 0.34% | +0.15% |
| 2 | 2026-06-15 | 0.02% | 0.19% | +0.17% |
| 3 | 2026-02-14 | — | 0.02% | — |
EPSS の全履歴 （全 3 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 7.8 | 3.1 | HIGH |
|
1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
| 7.8 | 3.1 | HIGH |
|
1.8 | 5.9 | [email protected] |
| 7.8 | 3.1 | HIGH |
|
1.8 | 5.9 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c |
GHSA-jh9m-9mr6-3ghc · 深刻度： high — In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix...
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
not yet assigned | CVE-2026-23111 not yet assigned priority: Debian including 2 source packages (linux, linux-6.1), 6 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 1. | https://security-tracker.debian.org/tracker/CVE-2026-23111 |
redhat
|
medium | — | https://access.redhat.com/security/cve/CVE-2026-23111 |
suse
|
high | CVE-2026-23111 severity important: SUSE including 582 source package names (2.1.3-6.124:kernel-default-base-6.4.0-40.1.21.17, 2.1.3-7.105:kernel-default-6.4.0-40.1, …), 879 product×package rows across 54 product lines (Container suse/sl-micro/6.0/base-os-container, Container suse/sl-micro/6.0/kvm-os-container, … (54 product lines)): Fixed 552, Known Affected 231, Known Not Affected 65, First Fixed 31. | https://www.suse.com/security/cve/CVE-2026-23111/ |
ubuntu
|
high | CVE-2026-23111 high priority: Ubuntu including 157 source packages (linux, linux-allwinner-5.19, …), 1256 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): DNE 871, ignored 169, released 157, not-affected 46, needed 8, pending 5. | https://ubuntu.com/security/CVE-2026-23111 |
| ベンダー | 製品 | バージョン | 生の CPE |
|---|---|---|---|
| linux | linux_kernel | >= 4.19.316, < 4.20 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 5.4.262, < 5.5 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 5.10.188, < 5.11 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 5.15.121, < 5.15.200 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.1.36, < 6.1.163 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.3.10, < 6.4 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.4.1, < 6.6.124 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.7, < 6.12.70 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 6.13, < 6.18.10 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | 6.4 | cpe:2.3:o:linux:linux_kernel:6.4:-:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:* |
| linux | linux_kernel | 6.19 | cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:* |