Skip to main content

Linux Kernel CVE-2026-68143

| EUVDEUVD-2026-55526 HIGH
2026-08-10 Linux GHSA-7xg5-v5hr-7r34
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) 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

Race condition requires precise timing coordination between MTU ioctl and receive callback, warranting AC:H over the vendor's AC:L; PR:L retained as minimum local access floor pending CAP_NET_ADMIN confirmation.

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:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
6.4 MEDIUM
AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Red Hat
7.3 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

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 14, 2026 - 01:59 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
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
HIGH 7.8

DescriptionCVE.org

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

net: slip: serialize receive against buffer reallocation

sl_realloc_bufs() replaces rbuff and updates buffsize while holding sl->lock. slip_receive_buf() reads those fields and writes through rbuff without holding the lock.

An MTU change can therefore race with receive processing. An MTU shrink can expose the new smaller rbuff with the old larger bound, causing an out-of-bounds write. A receive callback which already loaded the old rbuff can instead continue writing after that buffer has been freed.

Serialize receive processing with sl_realloc_bufs() by holding sl->lock while consuming each receive batch.

AnalysisAI

Race condition in the Linux kernel's SLIP (Serial Line Internet Protocol) driver allows a local attacker with low privileges to trigger an out-of-bounds write or use-after-free in kernel memory, potentially enabling privilege escalation. The slip_receive_buf() callback reads and writes the receive buffer rbuff without holding sl->lock, while sl_realloc_bufs() replaces that buffer under the lock during MTU changes - creating a classic TOCTOU window where an MTU shrink can cause writes beyond the new smaller buffer or into a freed allocation. No confirmed active exploitation exists (not in CISA KEV) and the EPSS score of 0.18% places this in the 7th percentile, though kernel memory corruption of this class carries inherent privilege escalation potential.

Technical ContextAI

The SLIP driver (net/slip/slip.c) in the Linux kernel manages per-interface receive and transmit ring buffers (rbuff, xbuff) that are reallocated when the interface MTU changes. sl_realloc_bufs() acquires the per-interface spinlock sl->lock, swaps in a new smaller or larger rbuff, and updates buffsize atomically from the lock holder's perspective. However, slip_receive_buf() - the TTY layer's receive callback - loads rbuff and buffsize and writes incoming packet data through rbuff without ever acquiring sl->lock. This is a classic TOCTOU (Time-of-Check-Time-of-Use) concurrency defect: if a receive callback loads the old rbuff pointer before the MTU change completes, it proceeds to write into either the freed former buffer (use-after-free) or with the old larger bound against the new smaller buffer (out-of-bounds write). Both primitives represent kernel heap corruption. The CPE cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:* and the affected commit range starting from 1da177e4c3f4 (the very first Linux git commit, 2005) indicate essentially all kernel versions are affected. The SLIP subsystem itself is a legacy serial-line networking driver dating to early Unix systems, rarely configured in modern deployments.

RemediationAI

Apply the vendor-released kernel patch corresponding to your stable branch: upgrade to Linux 6.6.148, 6.12.101, or 6.18.42 for LTS branches, or 7.1.6 and 7.2-rc5 for current mainline tracks; all patch commits are indexed in the kernel stable tree at the git.kernel.org links above. As an immediate compensating control for systems where patching is not yet possible, unload the SLIP kernel module (rmmod slip) and blacklist it via /etc/modprobe.d/blacklist-slip.conf with blacklist slip - this eliminates the attack surface entirely with no functional impact on any system not actively using serial-line networking, which is the vast majority of modern deployments. If SLIP must remain active, restricting the ability to call SIOCSIFMTU on SLIP interfaces (via seccomp-bpf policy or Linux Security Module rules limiting CAP_NET_ADMIN grants) reduces the window for triggering the race but does not eliminate it if privileged processes are the intended user. Distribution-specific advisories should be consulted via https://nvd.nist.gov/vuln/detail/CVE-2026-68143 for backported package versions.

Vendor StatusVendor

SUSE

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

Share

CVE-2026-68143 vulnerability details – vuln.today

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