Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1444ff890b4653add12f734ffeffc173d42862dd, 4.20, 42c574c1504aa089a0a142e4c13859327570473d.

Low priority for now. Upgrade to Linux Linux 1444ff890b4653add12f734ffeffc173d42862dd, 4.20, 42c574c1504aa089a0a142e4c13859327570473d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Feb 13, 2026
Updated
Oct 15, 2026
EPSS
1.1% · 67th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23111

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.19.316 and later · before 4.20
  • linux linux kernel5.4.262 and later · before 5.5
  • linux linux kernel5.10.188 and later · before 5.11
  • linux linux kernel5.15.121 and later · before 5.15.200
  • linux linux kernel6.1.36 and later · before 6.1.163
  • linux linux kernel6.3.10 and later · before 6.4
  • linux linux kernel6.4.1 and later · before 6.6.124
  • linux linux kernel6.7 and later · before 6.12.70
  • linux linux kernel6.13 and later · before 6.18.10
  • linux linux kernel6.19
  • linux linux kernel6.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • bc9f791d2593f17e39f87c6e2b3a36549a3705b1, 3c7ec098e3b588434a8b07ea9b5b36f04cef1f50, a136b7942ad2a50de708f76ea299ccb45ac7a7f9, dc7cdf8cbcbf8b13de1df93f356ec04cdeef5c41, 6.4affected
    • 25aa2ad37c2162be1c0bc4fe6397f7e4c13f00f8 and later · before 8c760ba4e36c750379d13569f23f5a6e185333f5affected · git
    • d60be2da67d172aecf866302c91ea11533eca4d9 and later · before b9b6573421de51829f7ec1cce76d85f5f6fbbd7faffected · git
    • 628bd3e49cba1c066228e23d71a852c23e26da73 and later · before 42c574c1504aa089a0a142e4c13859327570473daffected · git
    • 628bd3e49cba1c066228e23d71a852c23e26da73 and later · before 1444ff890b4653add12f734ffeffc173d42862ddaffected · git
    • 628bd3e49cba1c066228e23d71a852c23e26da73 and later · before 8b68a45f9722f2babe9e7bad00aa74638addf081affected · git
    • 628bd3e49cba1c066228e23d71a852c23e26da73 and later · before f41c5d151078c5348271ffaf8e7410d96f2d82f8affected · git
    • 5.15.121 and later · before 5.15.200affected · semver
    • 6.1.36 and later · before 6.1.163affected · semver
    • 4.19.316 and later · before 4.20affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23108Feb 4, 2026 · can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak
    22Monitor
  • ← EarlierCVE-2026-23110Feb 4, 2026 · scsi: core: Wake up the error handler when final completions race against each other
    18Monitor
  • Later →CVE-2026-23112Feb 13, 2026 · nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1444ff890b4653add12f734ffeffc173d42862ddVendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux42c574c1504aa089a0a142e4c13859327570473dVendor (CNA)
Linux Linux5.11Vendor (CNA)
Linux Linux5.15.200Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux6.1.163Vendor (CNA)
Linux Linux6.4Vendor (CNA)
Linux Linux8b68a45f9722f2babe9e7bad00aa74638addf081Vendor (CNA)
Linux Linux8c760ba4e36c750379d13569f23f5a6e185333f5Vendor (CNA)
Linux Linuxb9b6573421de51829f7ec1cce76d85f5f6fbbd7fVendor (CNA)
Linux Linuxf41c5d151078c5348271ffaf8e7410d96f2d82f8Vendor (CNA)
almalinux:kernel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.164-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.92.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.92.1.150600.12.42.2 · openSUSE:Leap 15.6Package registry (OSV)

+32

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×10

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-06-09
Proof-of-concept repository on GitHubstars:02026-06-09
Proof-of-concept repository on GitHubstars:52026-06-09
Proof-of-concept repository on GitHubstars:02026-06-10
Proof-of-concept repository on GitHubstars:22026-06-11
Proof-of-concept repository on GitHubstars:72026-06-25
Proof-of-concept repository on GitHubstars:12026-07-01
Proof-of-concept repository on GitHubstars:102026-08-12
Proof-of-concept repository on GitHubstars:02026-09-20
Proof-of-concept repository on GitHubstars:62026-10-19

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+115 d
  3. TodayNov 9, 2026+269 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records