Skip to main content

Linux Kernel EUVDEUVD-2026-59246

| CVE-2026-72347 HIGH
2026-08-15 Linux GHSA-5j52-34gv-x96c
High
Disputed · 7.3 Vendor: Linux
Share

Severity by source

Sources disagree (Low–High)
Vendor (Linux) PRIMARY
7.3 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
vuln.today AI
7.3 HIGH

Local access with CAP_NET_ADMIN (obtainable via user namespaces at PR:L); undefined-shift causes kernel integrity corruption (I:H) and crash potential (A:H) with minor info leak risk (C:L).

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

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

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

Lifecycle Timeline

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

DescriptionCVE.org

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

netfilter: xt_connmark: reject invalid shift parameters

Revision 2 of the CONNMARK target accepts user-controlled shift parameters and applies them to 32-bit mark values in connmark_tg_shift().

A shift_bits value of 32 or more triggers an undefined-shift bug when the rule is evaluated. Invalid shift_dir values are also accepted and silently fall back to the left-shift path.

Reject invalid revision-2 shift parameters in connmark_tg_check() so malformed rules fail at installation time, before they can reach the packet path.

AnalysisAI

Undefined-shift undefined behavior in the Linux kernel netfilter subsystem (xt_connmark) allows a local attacker with low privileges to trigger kernel crashes, potential memory corruption, and limited information disclosure. The flaw resides in the CONNMARK target revision 2, introduced in Linux 4.17, where user-supplied shift_bits values of 32 or greater are passed unchecked to 32-bit bitshift operations in connmark_tg_shift(), invoking C undefined behavior at packet-processing time. Exploitation is not confirmed active (not in CISA KEV) and EPSS sits at 0.21% (12th percentile), but the kernel-level impact and wide Linux deployment make patching a clear priority for exposed hosts.

Technical ContextAI

The affected component is the xt_connmark netfilter kernel module (CPE: cpe:2.3:a:linux:linux:*), specifically the CONNMARK iptables target at revision 2, which was introduced in commit 472a73e00757b971d613d796374d2727b2e4954d (Linux 4.17). Revision 2 added user-controllable shift_bits and shift_dir parameters that are applied to 32-bit connection mark values in connmark_tg_shift(). The root cause is the absence of input validation in connmark_tg_check(): a shift_bits value of 32 or more on a 32-bit integer invokes C language undefined behavior (ISO C11 §6.5.7), whose concrete result is architecture-dependent - on x86 the hardware ignores bits above 4 (masking mod 32) while on ARM the shift may produce zero, leading to inconsistent and unpredictable kernel state. Additionally, invalid shift_dir values are silently coerced to the left-shift code path, bypassing any intended directional logic. No CWE ID was assigned by NVD, but the class aligns with CWE-129 (Improper Validation of Array Index / Shift Count) and CWE-758 (Undefined Behavior). The fix enforces parameter rejection at rule-installation time in connmark_tg_check() so malformed rules never reach the packet path.

RemediationAI

The primary remediation is upgrading to a patched kernel version: 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, or 7.2-rc3, depending on the active stable branch. Upstream fix commits are indexed at https://git.kernel.org/stable/c/ for each stable tree. For systems where immediate kernel upgrade is not feasible, a targeted compensating control is to unload or blacklist the xt_connmark kernel module (modprobe -r xt_connmark; echo 'blacklist xt_connmark' >> /etc/modprobe.d/blacklist.conf) - this prevents the vulnerable code from being loaded entirely, though it will break any existing iptables/nftables rules that use the CONNMARK target. A second compensating control applicable to multi-tenant environments is disabling unprivileged user namespaces via sysctl -w kernel.unprivileged_userns_clone=0 (Debian/Ubuntu) or kernel.userns_restrict=1 where supported; this raises the effective privilege bar for rule installation back to root, though it may break container runtimes (e.g., rootless Podman, unprivileged LXC) that rely on user namespaces. Audit existing iptables/nftables ruleset for CONNMARK revision 2 rules with shift_bits >= 32 using iptables-save | grep CONNMARK.

Vendor StatusVendor

SUSE

Severity: Moderate
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 Affected

Share

EUVD-2026-59246 vulnerability details – vuln.today

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