Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-68121

7.8 · HIGH

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_har…

Published Aug 10, 2026EPSS 0.30%

Overview

CVE-2026-68121 is a high-severity vulnerability. It was published on August 10, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/6866abf59976d273164a6624234d96a967280223Refgit.kernel.org/stable/c/6eed5ae7887a93160803d2b81ff88e75eefd4a4cRefgit.kernel.org/stable/c/7a56e7c9b08e08fd55a1bcada24cf4fe3782b722Refgit.kernel.org/stable/c/7e9fbd7f96bcde63a7c798fe16b38cedee7a1501Refgit.kernel.org/stable/c/ba3409369c5413cdf0dcbf3a928f76b48e8c3e6aRefgit.kernel.org/stable/c/bed4caecd723693f750e13adbb2c42ca1249a3fdRefgit.kernel.org/stable/c/e6493a4d1ee17595766165fa446d45b7e0c318d0Refgit.kernel.org/stable/c/e9c238f6fe42fb1b4dba3a578277de32cb487937

How CyberStrike helps

Frequently asked questions

What is CVE-2026-68121?

CVE-2026-68121 is a high-severity vulnerability. It was published on August 10, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-68121?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-68121?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68121?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68121 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999