Skip to main content

Linux Kernel EUVDEUVD-2026-55547

| CVE-2026-68161 CRITICAL
2026-08-10 Linux GHSA-9g3f-gj9q-hqjj
Critical
Disputed · 9.8 Vendor: Linux
Share

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.8 MEDIUM

Local netns cleanup race needing CAP_NET_ADMIN (PR:L) and a hard-to-win teardown window (AC:H); primary impact is a kernel crash (A:H) with limited UAF-driven C/I risk.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
7.0 MEDIUM
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
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 01:32 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
9.8 (CRITICAL)
Patch available
Aug 10, 2026 - 14:18 EUVD
CVE Published
Aug 10, 2026 - 11:59 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 10, 2026 - 11:59 cve.org
CRITICAL 9.8

DescriptionCVE.org

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

sctp: close UDP tunnel sockets during netns teardown

proc_sctp_do_udp_port() starts per-net SCTP UDP tunneling sockets when net.sctp.udp_port is set, and stops/restarts them when the sysctl value changes. The netns exit path does not stop these sockets, so a namespace can be torn down while its SCTP UDP tunnel sockets are still installed.

Close the UDP tunnel sockets from sctp_ctrlsock_exit() after unregistering the per-net sysctl table. This prevents new sysctl writes from racing in while the sockets are being released, and closes the sockets before the control socket is destroyed.

AnalysisAI

Improper resource teardown in the Linux kernel's SCTP subsystem leaves per-net UDP tunnel sockets installed when a network namespace is destroyed, creating a use-after-free/dangling-socket condition once the control socket is released. The flaw affects systems where SCTP UDP encapsulation (net.sctp.udp_port) has been enabled inside a namespace before that namespace exits. There is no public exploit identified at time of analysis, EPSS is low (0.20%), and the issue is not in CISA KEV; the fix has already been merged to multiple stable trees. Note: the supplied 9.8/AV:N CVSS is inconsistent with the local, namespace-scoped nature of the actual defect.

Technical ContextAI

SCTP (Stream Control Transmission Protocol) supports UDP encapsulation (RFC 6951) so SCTP can traverse NAT/firewalls; the kernel spins up per-network-namespace UDP tunnel sockets when the net.sctp.udp_port sysctl is set, via proc_sctp_do_udp_port(). These sockets are started/stopped/restarted as the sysctl changes, but the namespace exit path (sctp_ctrlsock_exit) previously did not tear them down, so a netns could be destroyed while its tunnel sockets were still bound to now-freed per-net state - a lifetime/ordering bug of the resource-cleanup class (akin to CWE-416 use-after-free / CWE-404 improper resource shutdown). No CWE was assigned in the source data. The fix closes the tunnel sockets in sctp_ctrlsock_exit() after unregistering the per-net sysctl table, both to prevent racing sysctl writes and to release the sockets before the control socket is destroyed. Affected code is generic to the mainline SCTP stack; CPE data only generically identifies 'linux:linux' without precise version bounds.

RemediationAI

Upstream fix available and released in stable kernels - update to at least 6.6.151, 6.12.101, 6.18.42, or 7.1.6 (fix present in 7.2-rc5), matching your kernel branch; apply the distribution kernel package that incorporates the corresponding kernel.org commit (e.g. c6eb2d615210..., see https://git.kernel.org/stable/c/c6eb2d615210b80339548ab07c0230edaab9a6c7). As a compensating control until patched, avoid enabling SCTP UDP tunneling by leaving net.sctp.udp_port at 0 (the default), which prevents the per-net tunnel sockets from ever being created and thus avoids the teardown race - side effect: SCTP-over-UDP encapsulation will not function. Where SCTP itself is unneeded, blacklist the sctp module (e.g. install sctp /bin/true), which removes the attack surface entirely at the cost of disabling SCTP. On multi-tenant/container hosts, restrict unprivileged user-namespace creation (e.g. sysctl kernel.unprivileged_userns_clone=0 where available) to deny untrusted users the CAP_NET_ADMIN needed to set the sysctl, noting this may break sandboxes and container runtimes that rely on user namespaces.

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-55547 vulnerability details – vuln.today

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