Skip to main content

Linux Kernel EUVDEUVD-2026-55502

| CVE-2026-68121 HIGH
2026-08-10 Linux GHSA-7hvc-v975-w6v4
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 requiring concurrent PPPoE send and team device modification warrants AC:H; AV:L and PR:L reflect required local low-privilege access per description.

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
7.3 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 - 02:22 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:58 cve.org
HIGH 7.8
CVE Published
Aug 10, 2026 - 11:58 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

pppoe: reload header pointer after dev_hard_header()

pppoe_sendmsg() saves a pointer to the PPPoE header before calling dev_hard_header(). Device header callbacks are allowed to reallocate the skb head, invalidating pointers into it.

This can happen when a send is blocked in copy_from_user() while the first non-Ethernet port is added to an empty team device. The team's delegated GRE header callback then expands the skb head. PPPoE subsequently writes six bytes through the stale pointer into the freed head.

Reload the PPPoE header through the skb's network-header offset after device header creation. pskb_expand_head() updates that offset when it relocates the head.

AnalysisAI

Memory corruption in the Linux kernel PPPoE driver allows a local low-privilege attacker to write six bytes through a stale pointer into freed kernel memory, with potential for privilege escalation to root. The flaw exists in pppoe_sendmsg(), which saves a direct pointer to the PPPoE header before calling dev_hard_header() - a callback that may reallocate the socket buffer head, invalidating the saved pointer. This vulnerability is not confirmed actively exploited (not in CISA KEV), no public exploit is known, and EPSS stands at 0.18% (7th percentile); however, patches are available across multiple stable kernel series.

Technical ContextAI

The vulnerability resides in the PPPoE (Point-to-Point Protocol over Ethernet) subsystem of the Linux kernel, specifically in pppoe_sendmsg(). Socket buffers (skbs) in the Linux networking stack have a head region that can be reallocated by device header callbacks via pskb_expand_head(). The PPPoE driver incorrectly holds a direct pointer into this head across a call to dev_hard_header(), which for team devices with delegated GRE header callbacks performs exactly such a reallocation. The race condition materializes when a PPPoE send is blocked in copy_from_user() - a sleepable operation - while another thread concurrently adds the first non-Ethernet port to an empty team device, causing the GRE callback to expand the skb head. The PPPoE code then writes six bytes through the stale pointer into the former buffer location. The fix reloads the PPPoE header pointer via skb_network_header() after dev_hard_header() returns, since pskb_expand_head() correctly updates the skb's network-header offset upon relocation. While no CWE is formally assigned, the pattern matches CWE-825 (Expired Pointer Dereference) combined with a concurrent-access race, analogous to CWE-362. Affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*.

RemediationAI

Upgrade to a patched Linux kernel stable release - specifically Linux 6.6.148, 6.12.101, 7.1.6, 6.18.42, or 7.2-rc5 - as provided by your distribution vendor (Red Hat, Debian, Ubuntu, SUSE, etc.) or compiled from the kernel stable tree. Upstream fix commits are available at https://git.kernel.org/stable/c/e6493a4d1ee17595766165fa446d45b7e0c318d0 (branch-specific commits also at /7e9fbd7f96bcde63a7c798fe16b38cedee7a1501, /bed4caecd723693f750e13adbb2c42ca1249a3fd, /6866abf59976d273164a6624234d96a967280223, and /e9c238f6fe42fb1b4dba3a578277de32cb487937). If immediate patching is not feasible, eliminating the vulnerable code path by avoiding PPPoE over team devices that include non-Ethernet members (e.g., GRE tunnel ports) is the most effective compensating control, though this may require network reconfiguration. Additionally, restricting untrusted local users from CAP_NET_RAW capabilities via a policy enforcement tool (e.g., systemd service hardening, seccomp profiles) reduces the population of users who can open PPPoE sockets, but does not eliminate the vulnerability for privileged-enough local users.

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 Affected

Share

EUVD-2026-55502 vulnerability details – vuln.today

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