Skip to main content

Linux Kernel EUVDEUVD-2026-59151

| CVE-2026-72252 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-wp7x-h4hq-8jpw
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

AC:H because reliably triggering mid-clone allocation failure requires deliberate memory pressure engineering, not a straightforward API call; all other metrics match the local low-privilege kernel OOB write scenario.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 07:58 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:21 cve.org
HIGH 7.8
CVE Published
Aug 15, 2026 - 06:21 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nft_set_pipapo: don't leak bad clone into future transaction

On memory allocation failure the cloned nft_pipapo_match can enter a bad state:

  • some fields can have their lookup tables resized while others did

not

  • bits might have been toggled
  • scratch map can be undersized which also means m->bsize_max can be

lower than what is required

This means that the next insertion in the same batch can trigger out-of-bounds writes.

Furthermore, a failure in the first can result in the bad clone to leak into the next transaction because the abort callback is never executed in this case (the upper layer saw an error and no attempt to allocate a transactional request was made).

Record a state for the nft_pipapo_match structure:

  • NEW (pristine clone)
  • MOD (modified clone with good state)
  • ERR (potentially bogus content)

Then make it so that deletes and insertions fail when the clone entered ERR state.

In case the very first insert attempt results in an error, free the clone right away.

AnalysisAI

Out-of-bounds write in the Linux kernel's netfilter nft_set_pipapo component allows a local low-privileged attacker to corrupt kernel memory and potentially escalate to root. When memory allocation fails during cloning of an nft_pipapo_match structure inside a netfilter batch transaction, the clone can enter an inconsistent state - with mismatched lookup table sizes, toggled bits, or an undersized scratch map - and that corrupted clone can persist into the next transaction where a subsequent set insertion triggers an out-of-bounds write. No public exploit has been identified at time of analysis, and EPSS at 0.21% (11th percentile) indicates low predicted exploitation probability despite the high CVSS score of 7.8.

Technical ContextAI

The vulnerability resides in nft_set_pipapo, the 'Piece PAcket POlicy' multi-dimensional packet classifier used by the Linux kernel's nftables subsystem (netfilter). The pipapo algorithm stores lookup tables in nft_pipapo_match structures that are cloned at the start of each batch transaction to support transactional semantics. When a memory allocation fails mid-clone, fields such as the lookup table arrays, the scratch map, and bsize_max can be left in a partially updated state - some resized, others not - producing a structurally invalid clone. Critically, the abort callback that would normally discard this clone is never invoked when the upper layer observes an error before any transactional request is attempted, allowing the corrupt nft_pipapo_match to survive into the next transaction. The fix introduces a tristate status field (NEW, MOD, ERR) on the clone and enforces that insert and delete operations fail fast when ERR is set, with the first-insert-error path immediately freeing the clone. The root cause aligns with improper error-path cleanup in kernel memory management (no formal CWE assigned in this entry). Affected kernel versions begin at 5.6, which introduced the pipapo set type at commit 3c4287f62044a90e73a561aa05fc46e62da173da.

RemediationAI

The primary fix is to upgrade the Linux kernel to a patched stable release: 6.6.148, 6.12.97, 6.18.40, 7.1.5, or 7.2-rc2, as confirmed by EUVD and the upstream stable commits at https://git.kernel.org/stable/c/. Distribution-specific packages (Red Hat, Ubuntu, Debian, SUSE) will carry backported fixes under their own security advisories - consult your vendor's errata channels for the appropriate patched package version. As a compensating control where immediate patching is not feasible, administrators can disable unprivileged user namespace creation with 'sysctl -w kernel.unprivileged_userns_clone=0' (on distributions that expose this knob, such as Debian/Ubuntu), which raises the effective privilege bar from low to CAP_NET_ADMIN/root-level and prevents unprivileged users from accessing nftables configuration. Note that this control breaks rootless container workflows (Podman, rootless Docker, some sandbox engines) and may impact developer workstations more than servers. Alternatively, restricting nftables access via policy (SELinux, AppArmor, seccomp) to specific service accounts limits the attack surface without disabling user namespaces entirely.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

EUVD-2026-59151 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy